Combining Chaos, Observability & Resilience to get Chaos Engineering
summary
Chaos engineering is presented as an equation: observability + resilience = actionable chaos experiments. The talk defines resilience as four capabilities — monitor respond anticipate learn — and details seven observability attributes (logs, metrics, traces, telemetry, relevance, analytical insights, actions). A National Australia Bank experiment injects 40%, 60%, 80%, 100% packet loss into an AWS ECS microservice across three AZs, showing rising latency and error rates, confirmed timeouts at 100%, and unchanged container CPU/memory usage.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:25Agenda
- 2:21Example: US flight 1549
- 3:22Chaos foundations
- 5:53Observability
- 12:04Reliability & resilience
- 16:17Chaos engineering
- 22:56Outro
related talks
33mChaos Engineering, how to increase resilience by injecting chaos
26mBreaking Systems for Resilience
40mNavigating the Unknowable: Resilience through Security Chaos Engineering
18mChaos Engineering: Break It On Purpose
38mChaos Engineering: A Step Towards Resilience
36mChaos Engineering in 2021
38mChaos Engineering
21mThe Psychology of Chaos Engineering