You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ graph_count = 3
63
63
allow_legacy_url_auth = no
64
64
```
65
65
66
-
The local `http://127.0.0.1/<omd_site_name>` URL is recommended for the graph export. The bot first tries CheckMK's legacy internal graph renderer. If that renderer is not available, it uses the CheckMK Web `graph_image.py`PNG export endpoint with the automation credentials above. The bridge authenticates with HTTP auth headers so secrets are not sent in the URL. If a loopback HTTPS URL fails because the certificate is not valid for `127.0.0.1` or `localhost`, the bridge retries over local HTTP and, if the local web server redirects back to HTTPS, as a last resort retries the loopback HTTPS request without certificate verification. This relaxed TLS fallback is only used for loopback hosts. Missing graph support will not stop the bot or bridge service.
66
+
The local `http://127.0.0.1/<omd_site_name>` URL is recommended for the graph export. The bot first tries CheckMK's legacy internal graph renderer. If that renderer is not available, it tries CheckMK's notification graph endpoint `ajax_graph_images.py`and then the public `graph_image.py` PNG export endpoint. The bridge authenticates with HTTP auth headers so secrets are not sent in the URL. If a loopback HTTPS URL fails because the certificate is not valid for `127.0.0.1` or `localhost`, the bridge retries over local HTTP and, if the local web server redirects back to HTTPS, as a last resort retries the loopback HTTPS request without certificate verification. This relaxed TLS fallback is only used for loopback hosts. Missing graph support will not stop the bot or bridge service.
67
67
68
68
Existing installations are migrated automatically. Legacy configuration files are backed up before changes are made, and old site-local application files are moved to a `legacy-<timestamp>` directory below `/omd/sites/<omd_site_name>/local/share/checkmk-telegram-plus`.
0 commit comments