How To Have An Operational Incident (a crash course)
summary
Minimum viable incident response is concrete: automatic monitoring that pages a single point of contact (often a Slack slash command), a dispatcher-like role that assembles the right people via a directory of on-call shortcuts, and a named Incident Commander with sole authority who runs the response from an assembly channel with a fallback conference number. Empirically adopt four hour shifts, train everyone as potential commanders, and practice — real example: AWS creds checked into GitHub triggered an account-compromise workflow.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:07What would you do
- 1:44Coffee
- 2:05Welcome
- 2:28What is an emergency
- 2:49No one will die
- 3:44Urgent vs Important
- 4:07Danger or Consequences
- 4:25Emergency
- 6:48Assembling
- 8:38Application
- 9:01Monitoring
- 12:21Digital Site
- 13:27Assess
- 14:15Cooperation Delegation
- 14:52The Incident Commander
- 15:56Criteria
- 16:58Shifts
- 17:37Summary
- 18:14Training
- 19:16Next steps
- 19:47Burnout Factory
- 20:59Corporate Activism
- 22:11Incident Response Framework
- 23:45What actually happened
- 24:25Resources
- 25:27Books
- 26:04Acknowledgements
- 26:41Questions
related talks
28mHow to Have an Operational Incident (A Crash Course)
30mHow to have an operational incident a crash course
20mHow to Have an Operational Incident
33mDon't Panic! Effective Incident Response
15mIncident Ready: Chaos Engineer Your Incident Response
29mComposing the Response: Building an Incident Pipeline from Scratch
39mNavigating the Chaos: A Holistic Approach to Incident Management
19mHow to handle incidents at scale