viktor/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

monitoring: TechnitiumZoneCountMismatch — compare replicas only, exclude primary

Browse source 
Primary has only the Primary-type zones it owns (10). Replicas have those
+ built-in zones (localhost, in-addr.arpa reverse, etc.), so their count
(14) can never match primary. Alert expr compared max-min across all
instances, making it chronically firing.

Fix: instance!="primary" filter. The real signal this alert wants is
"did one replica drift from the others" — replica-to-replica comparison
captures that; primary was never comparable.
This commit is contained in:
Viktor Barzin 2026-04-19 22:15:55 +00:00
parent 4bedabb9e8
commit 9041f52b05
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
stacks/monitoring/modules/monitoring/prometheus_chart_values.tpl
View file

@ -1980,7 +1980,7 @@ serverFiles:
annotations: annotations:
summary: "Technitium zone-sync has not run successfully in >1h (last: {{ $value | humanizeDuration }} ago)" summary: "Technitium zone-sync has not run successfully in >1h (last: {{ $value | humanizeDuration }} ago)"
- alert: TechnitiumZoneCountMismatch - alert: TechnitiumZoneCountMismatch
expr: (max(technitium_zone_count) - min(technitium_zone_count)) > 0 expr: (max(technitium_zone_count{instance!="primary"}) - min(technitium_zone_count{instance!="primary"})) > 0
for: 15m for: 15m
labels: labels:
severity: warning severity: warning