How Did Things Go Right? Learning More from Incidents
summary
Argues SRE work shifts from chasing fixes to mapping how systems and teams succeed: use SLOs and error budgets for context, run chaos experiments until detection and recovery are seconds, then analyze incidents by listing contributing factors, documenting mitigations (auto‑scaling rescued signups), building artifacts and interactive timelines, run cross‑level learning teams and interviews to extract performance variability and the presence of adaptive capacity rather than hunting a single root cause.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:16Principles
- 6:04Root Cause
- 9:10Why
- 11:29Performance Variance
- 13:09Helicopter Rescue
- 14:25Availability
- 17:07Incidents
related talks
25mUnleashing the potential of SRE for modern operations
26mIncreasing the collaboration between SREs and Developers
31mThe Art of Turning Incidents into Opportunities
22mSRE and Risk management: a love story
42mDemystifying SRE and DevOps
15mSustainable Incident Management for happy SRE teams
22mSRE for Enterprises
42mSite Reliability Engineering as Systems Thinking