What is considered the best practice when working with alerting notifications?
The Prometheus alerting philosophy emphasizes signal over noise --- meaning alerts should focus only on actionable and user-impacting issues. The best practice is to alert on symptoms that indicate potential or actual user-visible problems, not on every internal metric anomaly.
This approach reduces alert fatigue, avoids desensitizing operators, and ensures high-priority alerts get the attention they deserve. For example, alerting on ''service unavailable'' or ''latency exceeding SLO'' is more effective than alerting on ''CPU above 80%'' or ''disk usage increasing,'' which may not directly affect users.
Option B correctly reflects this principle: keep alerts meaningful, few, and symptom-based. The other options contradict core best practices by promoting excessive or equal-weight alerting, which can overwhelm operations teams.
Verified from Prometheus documentation -- Alerting Best Practices, Alertmanager Design Philosophy, and Prometheus Monitoring and Reliability Engineering Principles.
Amber
4 months agoMurray
4 months agoLauran
4 months agoBok
4 months agoMyra
4 months agoNathalie
5 months agoOctavio
5 months agoCristina
5 months agoSabra
5 months agoMarion
6 months agoJulieta
6 months agoCecilia
6 months agoBlondell
6 months agoMichal
6 months agoCarlton
7 months agoJess
7 months agoKayleigh
7 months agoYasuko
7 months agoAnnamae
7 months agoJose
7 months agoJesus
8 months agoMelina
8 months agoJin
8 months agoAlba
8 months agoXuan
8 months agoEdmond
9 months agoYvette
3 months agoHershel
3 months agoMan
3 months agoJulian
3 months agoGail
3 months ago