Improving resilience through SLO validation using chaos engineering
summary
Claims continuous SLO validation with chaos engineering yields measurable resilience gains, using ChaosNative’s Litmus Chaos platform to run declarative experiments (fault + probe), auto-remediation and a chaos center for scheduling. Enterprises run ~1,000+ daily downloads of Litmus, report reduced MTTR/MDTF and wider safety margins, and Litmus 2.0 provides reusable experiments, probes and a computed resilience score so teams can see whether injected faults break SLIs and whether fixes actually improve recovery.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:16Reliability in modern systems
- 4:50Cloud native challenges
- 7:40Chaos engineering process
- 9:28Defining service level objectives and validation
- 12:18SLO validation in depth
- 15:08Chaos implementation process
- 16:32Litmus Chaos features
- 20:28Chaos Center workflow
- 22:14Shift-left chaos testing
- 23:16SLO validation in Litmus
- 25:04Continuous chaos validation
related talks
26mUnified Chaos Injection And SLO Validation Experiments In Kubernetes
32mPower Level 9000! Improving Application Performance with Chaos Engineering
37mUsing SLOs for Continuous Performance Optimizations of Your K8s Workloads
50mFrom Load Testing to Reliability Engineering: Making Performance Testing Predict Production Behavior
17mContinuous resilience: Managing your application risks
05mContinuous Stability Engineering
34mToward continuous resilience
13mBeyond observability: Using reliability scores to drive results