The Why, What, and How of Starting an SRE Engagement
summary
Engagement with Azure IoT starts by taking over half the on-call rotation (eight developers initially thrown in) and uncovers missing runbooks, tribal knowledge, and deployments that break on nearly every rollout. The team automates the weekly incident review, automated system review meeting, builds small self-diagnosis network tools, fixes core service bugs, and becomes self-sufficient supporting half the on-call. Outcomes: reduced operational toil, repeatable on-call playbooks, quarterly leadership syncs, and a roadmap to scale patterns across other services.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:11The Four Stories
- 2:37The Why
- 3:12Common Stories
- 4:12What We Learned
- 6:04Building Trust
- 9:03OnCall Rotation
- 9:33The Reality
- 10:18Lessons Learned
- 12:25Story 3 Long Call
- 13:29Story 3 Evaluation
- 14:34Story 3 Outcome
- 16:00Story 4 Outcome
- 19:22Story 6 Lessons Summary
- 21:00The Big Takeaway
- 21:51Conclusion
related talks
39mThe Life of On-Call, how SRE is changing DevOps
21mMove to Integrated SRE Ops at a Retail organization
23mSite Reliability Evangelism: Practice Start-up within an Established...
25mUnleashing the potential of SRE for modern operations
30mThe Path to SRE
28mHow to Do SRE When You Have No SRE
58mEnterprise Roadmap for SRE
43mWhere SRE Can Go Wrong