Skip to content

Commit

Permalink
Merge pull request #34 from mia-platform/fix/remove-infoinhibitor
Browse files Browse the repository at this point in the history
fix: remove infoinhibitor
  • Loading branch information
verdienansein authored Oct 10, 2024
2 parents f97f7ce + d7db078 commit dfa39c7
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 15 deletions.
2 changes: 1 addition & 1 deletion charts/monitoring/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
apiVersion: v2
name: monitoring
version: 2.2.4
version: 2.2.5
kubeVersion: ">= 1.20.0-0"
appVersion: v0.74.0
description: "A Kubernetes monitoring stack based on Prometheus Operator"
Expand Down
14 changes: 0 additions & 14 deletions charts/monitoring/templates/default-rules/general.rules.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -38,17 +38,3 @@ spec:
expr: vector(1)
labels:
severity: none
- alert: InfoInhibitor
annotations:
description: |
This is an alert that is used to inhibit info alerts.
By themselves, the info-level alerts are sometimes very noisy, but they are relevant when combined with
other alerts.
This alert fires whenever there's a severity="info" alert, and stops firing when another alert with a
severity of 'warning' or 'critical' starts firing on the same namespace.
This alert should be routed to a null receiver and configured to inhibit alerts with severity="info".
runbook_url: https://runbooks.prometheus-operator.dev/runbooks/general/infoinhibitor/
summary: Info-level alert inhibition.
expr: ALERTS{severity = "info"} == 1 unless on(namespace) ALERTS{alertname != "InfoInhibitor", severity =~ "warning|critical", alertstate="firing"} == 1
labels:
severity: none

0 comments on commit dfa39c7

Please sign in to comment.