Smarter Disasters: End-to-End Automation for Incidents
summary
Xero scales incident handling for 1.3 million orgs and >1,000 releases a year by turning customer reports into alerts via an issue report pipeline, routing incidents to owning teams and a regional SRE backstop, and enforcing on-call-as-code through the PagerDuty API. A Slack chat bot multivac guides triage, shows recent releases, sets severity, and populates a Google Doc postmortem; the system automates data capture and supports meta-analysis of recurring failure modes.
AI-written summary · about
chapters (12)
- 0:00Start
- 3:19Incident Management Goals
- 5:01The Alerting Process
- 8:28The Anatomy of an Alert
- 11:00Defence in depth
- 12:49On-Callas Code
- 14:39Using Chatops to Scale Incident Management
- 16:02Effective Communications through Multivac
- 17:26Improving Incident Response with Multivac
- 18:01Multivac: Under the Hood
- 18:36Part Three: Review
- 21:31Questions?
related talks
34mIncidents Happen
29mComposing the Response: Building an Incident Pipeline from Scratch
19mHow to handle incidents at scale
17mIncident Response @ Scale-Building a Next Generation SOC
22mHow I Automated Incident Management
26mDispatch: Crisis Management Automation
31mFuturistic Luxury Incident Response
20mHow to Have an Operational Incident