Tackling Alert Fatigue with SLOs
summary
Teams declare an alert cleanup sprint, examine the 10 most noisy alerts, and disable or defer anything nonactionable or success-only; many environments show tens of thousands of alerts per week and rely on AIOps to cluster them. After hygiene, SLOs introduce an error budget and let teams escalate only when the budget approaches depletion (for example alerting at ~97% instead of on the first failure), reducing wake‑ups and focusing human attention.
AI-written summary · about
chapters (6)
- 0:00Introduction and Speaker Information
- 0:49Understanding Alert Fatigue
- 4:23Signs and Consequences of Alert Fatigue
- 7:38Improving Alert Volume and Health
- 21:06Implementing SLOs to Combat Alert Fatigue
- 28:29Conclusion and Resources
related talks
27mWant to Solve Over-Monitoring...
39mActionable Observability
19mSensory Friendly Monitoring
43mSLO Burn—Reducing Alert Fatigue and Maintenance Cost in Systems of Any Size
41mA Theory and Practice of Alerting with Service Level Objectives
27mSensory Friendly Monitoring: Keeping the Noise Down
06mSensory Friendly Monitoring
30mOn call does not have to suck