Repository navigation
Unnecessary Kafka monitoring alerts triggered when Kafka is not deployed #790
Description
Description:
When deploying CozyStack without enabling or configuring Kafka, the included Kafka Prometheus rules (prometheus-kafka-rules) trigger constant alerts (e.g., ZookeeperContainersDown, TopicOperatorContainerDown, etc.), even though Kafka is intentionally not deployed.
Expected behavior:
Kafka-related alerts should only be active if Kafka (Strimzi) is explicitly enabled and deployed.
Suggested Solution:
Make Kafka-related VMRule or PrometheusRule CRDs conditional, based on whether Kafka is enabled, or clearly document steps to disable Kafka alerts in environments where Kafka isn’t deployed.
Current workaround:
Manually deleting or disabling Kafka monitoring rules.
Reacted by Nick Volynkin
Metadata
Metadata
Assignees
Labels
No labels
Activity
lllamnyp commentedon Apr 10, 2025
Hi @Identitry , thanks for looking into this. Looks like the alerting rules we vendored from upstream aren't really designed to be used as is. We'll discuss what can be done with the team.
If anyone in the community is interested in helping out, it'd be great to come up with a fix that doesn't require modifications in the upstream code. One option might be to have a dedicated instance of VMAlert watching over any given deployment of Kafka. The starting point would be somewhere here in the codebase.
[kafka] Disable noisy alerts (cozystack#1488)