Silencing deliberately suppresses notifications for selected alerts when an operational condition is already known, such as planned Kubernetes node maintenance. The alert may still fire, but its notification is suppressed proactively through Alertmanager. section 7.2.1
Silencing occupies one stage in Alertmanager’s notification pipeline:
- Inhibition suppresses related notifications when another alert is already firing; silencing suppresses notifications ad hoc before or during a known event. section 7.2.1
- Routing, grouping, throttling, and receivers determine who receives remaining notifications and how they are delivered. section 7.2.1
Planned Kubernetes node upgrade
During a node upgrade, nodes may go down temporarily. Creating a silence prevents predictable node-related notifications from distracting operators while the maintenance proceeds; unrelated alerts can continue through routing and delivery. section 7.2.1
Use the Prometheus–Alertmanager architecture diagram to locate silencing within the path from alert rules to notifications. section 7.2.1
