fix(rules/bootstrap): Format yaml

2025-12-29 13:23:04 +01:00
parent f81a4b2732
commit 957526a6bc
22 changed files with 2142 additions and 2044 deletions
@@ -1,43 +1,47 @@
 groups:
- name: general.rules
-  rules:
-  - alert: TargetDown
-    annotations:
-      description: '{{ printf "%.4g" $value }}% of the {{ $labels.job }}/{{ $labels.service
-        }} targets in {{ $labels.namespace }} namespace are down.'
-      runbook_url: https://runbooks.prometheus-operator.dev/runbooks/general/targetdown
-      summary: One or more targets are unreachable.
-    expr: 100 * (count(up == 0) BY (cluster, job, namespace, service) / count(up)
-      BY (cluster, job, namespace, service)) > 10
-    for: 10m
-    labels:
-      severity: warning
-  - alert: Watchdog
-    annotations:
-      description: |
-        This is an alert meant to ensure that the entire alerting pipeline is functional.
-        This alert is always firing, therefore it should always be firing in Alertmanager
-        and always fire against a receiver. There are integrations with various notification
-        mechanisms that send a notification when this alert is not firing. For example the
-        "DeadMansSnitch" integration in PagerDuty.
-      runbook_url: https://runbooks.prometheus-operator.dev/runbooks/general/watchdog
-      summary: An alert that should always be firing to certify that Alertmanager
-        is working properly.
-    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
+  - name: general.rules
+    rules:
+      - alert: TargetDown
+        annotations:
+          description:
+            '{{ printf "%.4g" $value }}% of the {{ $labels.job }}/{{ $labels.service
+            }} targets in {{ $labels.namespace }} namespace are down.'
+          runbook_url: https://runbooks.prometheus-operator.dev/runbooks/general/targetdown
+          summary: One or more targets are unreachable.
+        expr:
+          100 * (count(up == 0) BY (cluster, job, namespace, service) / count(up)
+          BY (cluster, job, namespace, service)) > 10
+        for: 10m
+        labels:
+          severity: warning
+      - alert: Watchdog
+        annotations:
+          description: |
+            This is an alert meant to ensure that the entire alerting pipeline is functional.
+            This alert is always firing, therefore it should always be firing in Alertmanager
+            and always fire against a receiver. There are integrations with various notification
+            mechanisms that send a notification when this alert is not firing. For example the
+            "DeadMansSnitch" integration in PagerDuty.
+          runbook_url: https://runbooks.prometheus-operator.dev/runbooks/general/watchdog
+          summary:
+            An alert that should always be firing to certify that Alertmanager
+            is working properly.
+        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