Ignore new watchdog collector of node-exporter

giantswarm · Aug 23, 2024 · 723d8b1 · 723d8b1
1 parent 12d4b70
commit 723d8b1
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -11,6 +11,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Assign alerts on core components directly to turtles.
 
+### Fixed
+
+- Ignore new `watchdog` collector of node-exporter since our clusters will not have data for these devices and therefore the `node_scrape_collector_success` metric would be 0
+
 ## [4.10.0] - 2024-08-20
 
 ### Changed

diff --git a/helm/prometheus-rules/templates/kaas/turtles/alerting-rules/node-exporter.rules.yml b/helm/prometheus-rules/templates/kaas/turtles/alerting-rules/node-exporter.rules.yml
@@ -14,7 +14,7 @@ spec:
       annotations:
         description: '{{`NodeExporter Collector {{ $labels.collector }} on {{ $labels.instance }} is failed.`}}'
         opsrecipe: node-exporter-device-error/
-      expr: node_scrape_collector_success{collector!~"conntrack|bonding|hwmon|powersupplyclass|mdadm|nfs|nfsd|tapestats|fibrechannel|nvme"} == 0
+      expr: node_scrape_collector_success{collector!~"conntrack|bonding|hwmon|powersupplyclass|mdadm|nfs|nfsd|tapestats|fibrechannel|nvme|watchdog"} == 0
       for: 5m
       labels:
         area: kaas