Topic: alerting
-
Alert hygiene for host monitoring: rate over threshold, failed units, and duration windows
A page should mean a human must act now; a host disk approaching full should page on its fill rate, not a fixed percentage that a slow-growing partition can sit near for months, and a threshold crossed for an instant should not page at all. Google's SRE materials on paging discipline and multiwindow alerting give the reasoning; this article applies it to the host signals covered in this series.
-
Alert routing: grouping, inhibition, silences and escalation policies
Between a firing alert and a phone lie four decisions: which team and channel receive it (routing tree), which alerts travel together (grouping with group_wait, group_interval and repeat_interval), which are muted because a cause alert already explains them (inhibition) or because maintenance is planned (silences), and how long a responder has before the page escalates to the next person.
Machine-readable: JSON