From Monitoring to Observability: Left Shift your SLOs with Chaos
summary
Argues that SLOs belong in CI/CD by showing a C++ memory-leak bug that only appears under DNS failures, detected by instrumented metrics and a Prometheus pipeline; uses GitLab CI/CD to build images, Prometheus + PromQL (promcal/openslo) for SLOs and quality gates, and blocks deployments when objectives fail. Demonstrates chaos by scheduling DNS faults with Litmus/Chaos Mesh and explains handling Docker Hub rate limits, error budgets, and rollbacks.
AI-written summary · about
chapters (10)
- 0:00Intro
- 2:19Something goes wrong
- 4:48Switching to Ops
- 7:03Rate Limits
- 15:27Chaos
- 16:23Chaos Litmus
- 18:36Chaos Engineering
- 19:45Chaos Experiments
- 20:55Demo
- 28:51Observability
related talks
30mFrom Monitoring to Observability: Left Shift your SLOs with Chaos
40mScaling SLOs with Kubernetes and Cloud Native Observability
31mServerless Observability: a case study of SLOs
36mConfidence with Chaos for Your Kubernetes Observability
27mPutting Chaos Into Continuous Delivery to Increase App...
05mReducing Trauma in Production with SLOs and Chaos Engineering
26mUnified Chaos Injection And SLO Validation Experiments In Kubernetes
29mReducing Trauma in Production