How to Have an Operational Incident (A Crash Course)
summary
A concrete minimum viable incident response: monitoring and alerting (confidence often ~60%), a single, publicized chat‑ops or hotline that reaches a dispatcher/incident commander, an incident commander with sole authority who coordinates teams and records changes, and a backup communications site (slack primary, permanent Google Hangout backup). Define customer‑impact thresholds, 4‑hour shifts, criteria for “done” (mitigation vs full fix), and train engineers as incident commanders; an AWS creds leak example shows these steps catch real problems.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:36What would you do
- 0:52Case number blah
- 1:26If this happened at your company
- 2:16Nobodys Gonna Die
- 3:47Urgent vs Important
- 4:20Emergency
- 5:33Thinking Takes Time
- 6:11Emergency Signs
- 7:20Response Framework
- 8:05What Have We Learned
- 9:19Lets Apply This
- 9:38Monitoring
- 10:20Engagement
- 12:20Where to Go
- 13:37Assessing the Situation
- 14:27Cooperation Delegation
- 15:18Incident Commander
- 16:18Criteria for knowing when youre done
- 17:26Operational Incentives
- 18:02Summary
- 18:34Training
- 19:22Communication
- 20:58What Happened
- 21:48Further Resources
- 23:39Questions
related talks
30mHow To Have An Operational Incident (a crash course)
30mHow to have an operational incident a crash course
20mHow to Have an Operational Incident
19mHow to handle incidents at scale
33mDon't Panic! Effective Incident Response
27mManaging Incidents
39mNavigating the Chaos: A Holistic Approach to Incident Management
26mMastering Incident Communications