Epistemology of Incidents and Problem Solving
summary
Start-to-finish playbook for high-pressure incident work with concrete rules: codify alert routing, severity matrices and SLO intent; use Google SRE incident loop and tracing to do source-to-sink and binary searches; check Sentry, Datadog, ELB, VPC flow logs and Stackdriver for inconsistencies that carry signal; prefer quick reversible actions (rollback, scale‑up, failover) — example: APAC edge shows 10% timeouts and 500 alarms while app logs look normal; structure timestamped notes and tests so a feature flag drop 70% is clearly provable or falsified.
AI-written summary · about
chapters (11)
- 0:00Incident epistemology intro
- 1:01Knowledge in incident response
- 3:06Incident loop framework
- 3:48Codifying response standards
- 7:38Survival and triage
- 9:22Structured evidence systems
- 15:37Hypothesis testing
- 20:33Designing incident tests
- 27:12Incident management best practices
- 29:01Advanced incident communication
- 34:17Summary and key takeaways
related talks
15mIncident Ready: Chaos Engineer Your Incident Response
32mIncident Management - Talk the Talk, Walk the Walk
19mStorytelling as an Incident Management Skill
13mThe Incident Is The Way: Using Your Incidents to Win...
25mWhat I Learned
47mPersistent SRE Antipatterns: Pitfalls on the Road to Creating a Successful
23mSite Reliability Evangelism: Practice Start-up within an Established...
44mPanel: Peak Performance Under Pressure: Building Cross-Functional Resilience in Incident Response