Aller au contenu

AlertmanagerConfigInconsistent#

This alert is triggered when Alertmanager instances within the same cluster have different configurations.

Context#

In Caascad and NGOT, Alertmanager is deployed as a cluster.

There are therefore several instances of Alertmanager.

So for a cluster of two instances, the alert is triggered if the configuration of instance 0 is different from instance 1.

Troubleshooting Hints#

Tip

Below, <monitoring_namespace> can be:

  • Zone Cloud: monitoring, monitoring-client or monitoring-app
  • Zone Infra: monitoring or monitoring-consumption

More information in Caascad namespaces naming.

  • Notice the namespace label in the alert

Check Alertmanager configuration#

For each Alertmanager instance, check Alertmanager configuration and check if there are any differences.

kubectl exec -it -n <monitoring_namespace> <alertmanager_pod_0> -c alertmanager -- cat /etc/alertmanager/alertmanager.yml
kubectl exec -it -n <monitoring_namespace> <alertmanager_pod_1> -c alertmanager -- cat /etc/alertmanager/alertmanager.yml