Skip to content

PrometheusBadConfig

Jump to bottom
Paweł Krupa edited this page Apr 19, 2021 · 1 revision

PrometheusBadConfig

Meaning

Alert fires when Prometheus cannot successfully reload the configuration file due to the file having incorrect content.

Impact

Configuration cannot be reloaded and prometheus operates with last known good configuration. Configuration changes in any of Prometheus, Probe, PodMonitor, or ServiceMonitor objects may not be picked up by prometheus server.

Diagnosis

Check prometheus container logs for an explanation of which part of the configuration is problematic. Usually this can occur when ServiceMonitors or PodMonitors share the same job label.

Mitigation

Remove conflicting configuration option.

This wiki is DEPRECATED, all alerts were moved to https://github.com/prometheus-operator/runbooks and are available via https://runbooks.prometheus-operator.dev/ website.

Clone this wiki locally