LokiNotConnectedToAlertmanagers#
This alert is triggered when Loki Ruler instances have no (or not enough) connections to Alertmanager.
There are two severities:
- warning : Loki is not connected to at least one Alertmanager
- critical : Loki is not connected to any Alertmanager
Note
It's normal to see fake in the labels or description of the alert: this corresponds to the default name of the tenant in Loki.
Troubleshooting#
Check Loki configuration#
kubectl get cm -n <loki_namespace> -o yaml | grep alertmanager_url # Notice the namespace label in alert
Check that there are :
- 2 URLs for client zones
- 4 URLs for corp zones (
ngot_contract=obs-corp-stgorobs-corp-prd)
Example for client zone: http://alertmanager-0.alertmanager-headless.monitoring-stack-client-obs-test04:9093,http://alertmanager-1.alertmanager-headless.monitoring-stack-client-obs-test04:9093