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
When relating Prometheus to a charm that provides alert rules (for instance cos-configuratior) and some of the alert rules are not well formatted, Prometheus silently does not load those alert rules.
So for instance if you relate prometheus to cos-configurator with this alert rule where the expr is wrongly indented, the alert rule is silently not loaded into Prometheus.
groups:
- name: Custom JVM Rulesrules:
- alert: Custom JVM Usageannotations:
description: " The broker {{ $labels.instance }} has high memory usage ({{ $value }}>85%) for more than 10 minutes."summary: "Broker {{ $labels.instance }} :: Critical :: Memory usage is {{ $value }}%"expr: ((sum without(area)(jvm_memory_bytes_used{juju_charm!=".*"}) / 1024 / 1024) / (sum without(area)(jvm_memory_bytes_max{juju_charm!=".*"}) / 1024 / 1024)) * 100 > 85for: 5mlabels:
severity: critical
Enhancement Proposal
When relating Prometheus to a charm that provides alert rules (for instance
cos-configuratior
) and some of the alert rules are not well formatted, Prometheus silently does not load those alert rules.So for instance if you relate
prometheus
tocos-configurator
with this alert rule where theexpr
is wrongly indented, the alert rule is silently not loaded into Prometheus.Related issues:
The text was updated successfully, but these errors were encountered: