Improve Application Resilience using Azure Chaos Studio
summary
Azure Chaos Studio validates resilience by running hypothesis-driven fault injections across Azure using a VM agent and service-direct faults (Service Bus, Redis, Cosmos DB, AKS), exporting telemetry to Log Analytics. Demo builds an experiment with VM shutdown fault (5 minutes) targeting three zone-spread VMs via KQL dynamic targeting, observes one zone recovering slower and overall availability falling to sub-10% data availability when all three zones go down, then sees the resources return to healthy state. Continuous validation and drill automation are emphasized.
AI-written summary · about
chapters (12)
- 0:00Introduction to Chaos Studio
- 1:29Shared Responsibility Model
- 2:40Chaos Engineering Principles
- 4:05Common Use Cases
- 5:08Experiment Key Elements
- 7:52Azure Chaos Studio Overview
- 9:53Fault Types and Disruptions
- 11:50Scenario-Based Testing
- 13:06Getting Started Recommendations
- 15:24Demo: Setting Up Experiment
- 20:26Demo: Running and Monitoring
- 23:53Conclusion
related talks
34mResilient Cloud App: Chaos Engineering, Azure Studio
45mApplication reliability with Azure Load Testing and Chaos Studio Q&A
33mChaos Engr at Microsoft with Azure Chaos Studio
32mImplementing Chaos Engineering in Kubernetes
34mStress-Test tools in Azure to optimize your reliability
26mImprove application resilience with chaos engineering
59mBuilding Resilient Applications In Microsoft Azure
01h 01mEmbrace chaos to achieve stability