Bring Chaos to Your Org
summary
Electrolux consolidates multiple observability stacks into Datadog, runs a CTF-style chaos gameday with 41 developers from 12 teams across 4 countries and seven experiments, and reports incidents falling ~33% after follow-up work. They build an IDP with Backstage and Terraform templates and add a chaos button that triggers experiments via Litmus Chaos 3.0, records hypotheses, and feeds results into the observability platform; next steps focus on automation and scalable fault-model libraries.
AI-written summary · about
chapters (19)
- 0:00intro
- 0:22preamble
- 0:32about kristina and long
- 0:47agenda
- 0:57electrolux and its iot systems
- 3:46bring chaos engineering step-by-step
- 4:05step 1: connect the 'islands'
- 7:16step 2: play and learn
- 8:20preparation
- 10:33flow for experiment execution
- 12:24tricks of experiment design
- 14:37sumary of the chaos gameday
- 15:26feedback from players
- 17:02how to reduce effort / things that can be improved?
- 17:40step 3: chaos ops platform engineering
- 19:59chaos ops mvp - embedded in idp
- 21:06scalable approach with litmus chaos 3.0
- 21:58next steps
- 22:35thank you!
related talks
26mFrom experimentation to continuous verification
46mEmbracing Collaborative Chaos: Chaos Days on Large Platforms
19mChaos Engineering at Scale
30mBringing Order to Chaos: Make Your Systems More Resilient with Chaos Engineering
18mFostering Chaos Engineering Culture
34mChaos Engineering For Hybrid Targets With LitmusChaos
32mAre you hesitant to run chaos experiment...
05mProject Lightning Talk: Chaos Unleashed: LitmusChaos and Its Journey Towards CNCF Graduation