From d7db078bc08414d3dbfa52d71217985bd349e204 Mon Sep 17 00:00:00 2001 From: Guglielmo Carnemolla Date: Thu, 10 Oct 2024 12:48:56 +0200 Subject: [PATCH] fix: remove infoinhibitor --- charts/monitoring/Chart.yaml | 2 +- .../templates/default-rules/general.rules.yaml | 14 -------------- 2 files changed, 1 insertion(+), 15 deletions(-) diff --git a/charts/monitoring/Chart.yaml b/charts/monitoring/Chart.yaml index f20b70b..307598a 100644 --- a/charts/monitoring/Chart.yaml +++ b/charts/monitoring/Chart.yaml @@ -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" diff --git a/charts/monitoring/templates/default-rules/general.rules.yaml b/charts/monitoring/templates/default-rules/general.rules.yaml index 5049896..ce79ce8 100644 --- a/charts/monitoring/templates/default-rules/general.rules.yaml +++ b/charts/monitoring/templates/default-rules/general.rules.yaml @@ -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