SRE and Risk management: a love story
summary
Molly treats DORA as actionable SRE work: inventorying systems via Backstage catalog info.yml and standardized tags, piping telemetry through an observability pipeline, and linking distributed traces to synthetic tests to map business functions. SLO work uses Google's art of SLO with 2–3 hour workshops; scorecards use binary checks. Incidents run through a Slack incident bot that pages, drafts postmortems and computes lost transactions. Resilience testing is tiered (3 tiers) with 2‑hour team gamedays and chaos injected by Chaos Controller (Datadog).
AI-written summary · about
chapters (7)
- 0:00SRE and risk management
- 1:08Risk management basics
- 3:57DORA requirements
- 7:27Critical assets identification
- 11:19DORA incident processes
- 14:53Resiliency testing
- 19:53Key learnings
related talks
42mDemystifying SRE and DevOps
22mSRE for Enterprises
26mIncreasing the collaboration between SREs and Developers
30mHow Did Things Go Right? Learning More from Incidents
21mSRE, what is it all about?!
42mDemystifying SRE and DevOps
25mUnleashing the potential of SRE for modern operations
21mMaximizing resilience through SRE and governance: A holistic approach
