-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Closed
Labels
Description
Describe the bug a clear and concise description of what the bug is.
Hey! We love the newest release with the rule inhibition feature. We sadly see rule evaluation failures:
ts=2022-02-07T14:42:17.636Z caller=manager.go:609 level=warn component="rule manager" group=general.rules msg="Evaluating rule failed" rule="alert: InfoInhibitor\nexpr: ALERTS{severity=\"info\"} == 1 unless on(namespace) ALERTS{alertname!=\"InfoInhibitor\",alertstate=\"firing\",severity=~\"warning|critical\"}\n == 1\nlabels:\n severity: none\nannotations:\n description: |\n This is an alert that is used to inhibit info alerts.\n By themselves, the info-level alerts are sometimes very noisy, but they are relevant when combined with\n other alerts.\n This alert fires whenever there's a severity=\"info\" alert, and stops firing when another alert with a\n severity of 'warning' or 'critical' starts firing on the same namespace.\n This alert should be routed to a null receiver and configured to inhibit alerts with severity=\"info\".\n runbook_url: https://runbooks.prometheus-operator.dev/runbooks/general/infoinhibitor\n summary: Info-level alert inhibition.\n" err="vector contains metrics with the same labelset after applying alert labels"
What's your helm version?
3.8.0
What's your kubectl version?
1.23
Which chart?
kube-prometheus-stack
What's the chart version?
v32
What happened?
No response
What you expected to happen?
No response
How to reproduce it?
No response
Enter the changed values of values.yaml?
No response
Enter the command that you execute and failing/misfunctioning.
none
Anything else we need to know?
No response
ebuildy