Putting Gremlins in the Pipes: How to Automate Chaos Engineering
summary
Shows how to automate chaos with Gremlin agent + CLI and embed attacks as a Jenkins pipeline step, exporting configured experiments (example: CPU/memory spike on 3–5 nodes) and gating deploys with automated health checks / stop criteria. Argues start-small then scale to production, run recurring experiments to prevent regressions, and cites costs of outages (Amazon $220k/min example, British Airways $73M market cap hit) to justify automation.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:28Historical failure examples
- 8:33Cloud systems evolution
- 13:59What is chaos engineering
- 22:49Common excuses
- 26:52Getting started
- 33:17Sustaining chaos experiments
- 36:37Automation and integration
- 42:20Chaos in CI/CD pipeline
- 45:02Call to action
related talks
21mSelf-Service Chaos Engineering: Fitting Gremlin into Grubhub's DevOps Culture
29mThe Road to Reliability
18mFostering Chaos Engineering Culture
52mGetting started with Chaos Engineering
27mImplementing Chaos Engr. in a Risk Averse Culture
18mChaos Engineering: Break It On Purpose
23mHow to tame chaos effectively?
29mImprove Resilience with automated chaos engineering