Chaos Experiments under the lens of AIOps
summary
MiniKube ecommerce demo with ~10–11 microservices uses Splunk Observability + an AIOps layer, litmuschaos to inject 4,000 ms network latency into the card service for 200s, and locust simulating 30 users (spawn rate 2). Splunk detects and alerts on latency and issues a prediction before the peak, a dashboard counts litmus-triggered pod launches, and a runbook can auto-remediate (rebuild/reset). Hypothesis that AIOps recognizes and responds to chaos experiments is proven by the live demo.
AI-written summary · about
chapters (10)
- 0:00AIOps and chaos engineering intro
- 1:04AIOps vs chaos engineering
- 3:09AIOps observe engage act model
- 5:13Planning chaos experiments
- 6:37Setting chaos hypothesis
- 8:00Live demo environment
- 10:25Injecting latency with Litmus Chaos
- 13:18AIOps response to chaos
- 16:30Detecting chaos via observability
- 17:13Summary
related talks
30mBringing Order to Chaos: Make Your Systems More Resilient with Chaos Engineering
26mUnified Chaos Injection And SLO Validation Experiments In Kubernetes
39mPracticing Cloud-Native Resliency Is a Challenge: Decoding It with Chaos...
34mChaos Engineering For Hybrid Targets With LitmusChaos
26mCanonical chaos through Litmus
39mResilience & Chaos Engineering in the Cloud
01h 01mMastering Resilience Probes: Simplify chaos hypot...
37mBringing order to the chaos!
