What to do when complex systems fail: A guide to chaos management
summary
Title gives specifics: a production log aggregator ran out of disk space causing reports to fail and a two‑hour escalation where 16 engineers on a Friday night all chase the same last Git commit. Framework maps to NIMS roles (incident commander, deputy, scribe, customer liaison, SMEs), ties outages to business metrics (PagerDuty uses outgoing notifications/sec), and recommends prework like Failure Friday simulations plus automation and chatops — e.g. a chatops command to start a major incident that pages roles so fixes (cron, monitoring) get built and human time is spared.
AI-written summary · about
chapters (38)
- 0:00Introduction
- 1:07What are complex systems
- 2:25How complex systems fail
- 3:51Structure of the talk
- 4:54Chapter 1 Failure
- 5:52Chapter 1 Incident
- 7:18Chapter 2 Dark and Stormy Night
- 8:25Chapter 3 The Soup
- 10:29Chapter 4 The Morning After
- 12:20Chapter 5 Lessons Learned
- 16:23Chapter 7 National Incident Management Systems
- 17:25Chapter 8 Single Responsibility Principle
- 18:17Chapter 9 Incident Calls
- 20:10Chapter 11 Incident Commander
- 21:37Chapter 12 Incident Commander
- 22:24Chapter 13 Divide Conquer
- 23:06Chapter 14 Communicate Effectively
- 24:08Chapter 15 Avoid the bystander effect
- 25:02Chapter 16 Reduce scope
- 26:10Chapter 17 Maintain order
- 26:30Chapter 18 The Deputy
- 27:50Chapter 19 The Deputy
- 28:52Chapter 20 The Scribe
- 29:07Chapter 21 The Scribe
- 30:24Chapter 22 The Customer Liaison
- 31:51Chapter 23 The Customer Liaison
- 32:38Chapter 24 The Customer Liaison
- 33:02Chapter 25 The Incident Commander
- 33:38Chapter 26 The Morning After One
- 34:37Chapter 27 Reliability
- 34:55Chapter 28 Role of Incident Commander
- 36:02Chapter 29 Role of Incident Commander
- 36:51Chapter 30 Wartime vs Peacetime Expectations
- 37:59Chapter 31 The Reveal
- 38:15Chapter 32 The Framework
- 38:37Chapter 33 Develop on call empathy
- 39:33Chapter 34 People are most valuable asset
- 41:04Chapter 35 How do you manage late events
related talks
42mPlan for Unplanned Work: Game Days with Chaos Engineering
39mNavigating the Chaos: A Holistic Approach to Incident Management
15mIncident Ready: Chaos Engineer Your Incident Response
47mChaos Engineering Bottom Up
23mHow to tame chaos effectively?
20mHow to Have an Operational Incident
26mBreaking Systems for Resilience
39mOops!… We F*ed It Up Again: The Art of Staying Calm When Systems Crash
