Father Beaver, Tell Us a Story (about OPS)
summary
Examines major outages from the last decade (GitHub, Amazon, Google, OVHcloud, Apple, Fastly, Microsoft, GitLab, Meta/Facebook) by reading their published post-mortems to identify root causes, corrective actions, and operational lessons. Uses post-mortem analysis techniques to extract concrete remediation steps and best practices for improving reliability and incident response in ops.
AI-written summary · about
chapters (18)
- 0:00Welcome to OPS story
- 2:10Team and Data OPS role
- 3:58Post mortem importance
- 6:06Elliot’s critical commands
- 9:202017 Vimeo incident
- 12:32On-call with legacy server
- 17:16Abandoned server risks
- 18:31CDN incident worldwide
- 21:45SPF weaknesses in systems
- 24:57Berlitz payment error India
- 26:06Java legacy app incident
- 29:22CDN network fixes
- 30:47Facebook BGP incident
- 34:44Avoid critical incidents
- 36:08Twitch security incidents
- 38:15Modern tech security risks
- 40:10Blow-up effect in tools
- 41:36Conclusion for OPS teams
related talks
01h 39mPostOps: A Non-Surgical Tale of Software, Fragility, and Reliability
22mAfter Death
30mLearning From Failure: Post Mortems
40mKeynote 'How to explain DevOps to your mom and how it works at Facebook, PayPal and others!'
55mDevOps @Scale (Greek Tragedy in 3 Acts)
48mDevops@Scale
40mDistilled Abnormal DevOps Iterations
37mBlameless Incidents: Learning from Failure at Scale