Sustainable Incident Management for happy SRE teams
summary
Lists concrete practices and one concrete tool: use automated draft postmortems via Datadog that pull metrics logs dashboards and Slack history, adopt an incident command hierarchy with clear commander/communicator roles, grade events with sev levels to trigger escalation and cross-team pulls, prefer shorter shifts like 12-hour on-call cycles and multi-tier backup, keep playbooks/runbooks and shadowing for ramp‑up, and run game days so procedures and automation actually work under pressure.
AI-written summary · about
chapters (12)
- 0:00Sustainable incident management
- 1:16Incident management importance
- 3:02Sustainability in response
- 4:05Incident commanders role
- 5:08On-call challenges and stress
- 6:52Tiered on-call systems
- 7:12Incident severities
- 8:57New responder onboarding
- 11:02Incident response practice
- 11:43Improving incident communication
- 13:07Automating postmortems
- 14:11Key takeaways
related talks
31mThe Art of Turning Incidents into Opportunities
25mUnleashing the potential of SRE for modern operations
28mHow to Do SRE When You Have No SRE
43mLearning from Firefighters to Improve Systems Reliability
42mDemystifying SRE and DevOps
30mHow Did Things Go Right? Learning More from Incidents
30mHow to have an operational incident a crash course
22mSRE and Risk management: a love story