Error Culture with Ryan Cheley
summary
Defines alerts, measures damage from alert fatigue, and gives concrete fixes: ask whether each alert is important, whether it contains a clear verb (reboot, rollback) and whether it goes to the people who can act. Shows sample subject lines evolving into best form, attaches knowledge‑base links, recommends converting recurring noise into a tracked issue or raising thresholds, and invokes Chesterton's fence to avoid blind removal of existing alerts.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:27Defining error culture
- 3:13Why error culture harms
- 4:16Root causes
- 6:43When error culture starts
- 8:54Signs of error culture
- 11:23Fixing error culture
- 12:05Understanding alerts
- 13:07Evaluating alerts
- 14:34Making alerts actionable
- 18:05Who should receive alerts
- 19:53Alert principles
- 20:37Q&A: Performance alerts
- 22:04Q&A: Spurious security alerts
- 24:13Q&A: Lessons for docs
related talks
28mAlerts don't suck, YOUR alerts suck
19mSensory Friendly Monitoring: Keeping the Noise Down
31mAlerts Don't Suck YOUR Alerts Suck!
31mBetter Monitoring for Humans: The CASE Method
06mSensory Friendly Monitoring
50mApplied Alerting Philosophy
32mWho Are Your Alerts For?
33mTackling Alert Fatigue with SLOs