Have you seen Azure Chaos Studio? If not, soon you have.
Table of Contents
What is Chaos Studio?
Chaos Studio is a managed service that employs chaos engineering to assist you in measuring, understanding, and improving the resilience of your cloud applications and services. Chaos engineering is a technique for injecting real-world faults into your application in order to run controlled fault injection experiments.
Chaos Studio assists you in avoiding negative consequences by validating that your application responds to disruptions and failures effectively.
What new in January 2023
How to setup?
Chaos Studio resource provider
If you are using Chaos Studio for the first time, you must first register the Chaos Studio resource provider before on-boarding resources and creating an experiment. This must be done for each subscription where Chaos Studio will be used.
- Open the Azure portal.
- Search for Subscriptions and open the subscription management page.
- Click on the subscription where you will be using Chaos Studio.
- In the left-hand navigation, click on Resource providers.
- In the list of resource providers that appears, search for Microsoft.Chaos.
- Click on the Microsoft.Chaos provider, and click the Register button.
Create a resource and give it Contributor permissions for Chaos Studio Managed Identity
Choose the Identity
Once done, open Chaos Studio from https://portal.azure.com/#view/Microsoft_Azure_Chaos/ChaosStudioMenuBlade/~/overview/defaultMenuItem/chaosExperiment
Create an experiment
Create an experiment inside Chaos Studio. A chaos experiment is an Azure resource that describes the faults to be run and the resources against which those faults should be run.
What we are trying today?
The Key Vault Deny Access error prevents all network access to a Key Vault by temporarily changing the network rules of the Key Vault, prohibiting an application that relies on the Key Vault from accessing secrets, keys, and/or certificates.
Continue adding your Key vault as a Target
Once added, you will it as a Chaos target
Then you proceed to add a Fault to the logic. Every activity that occurs as part of an experiment is referred to as an action in Chaos Studio, and the most common type of action is a fault.
Add a target for the Fault. A chaos target allows Chaos Studio to interact with a specific target type’s resource. The method of injecting faults against a resource is represented by a target type.
And finally create the experiment.
Once done start to invoke the Logic. An experiment is divided into steps that are performed one after the other. Each step has one or more concurrently running branches. Steps and branches enable you to simultaneously inject multiple faults across resources in your environment.
And be warned about causing problems but we already know what were are doing
See those problems processing from the overview page
And the completed Chaos will show you the results and duration
This feature is still in Preview, so there will be some limitations, see more here.
Chaos engineering is a methodology that assists developers in achieving consistent reliability by hardening services against production failures. Another way to think about chaos engineering is to embrace the inherent chaos in complex systems and gain confidence in your solution’s ability to handle it through experimentation.
Intentionally introducing faults that cause system components to fail is a common way to introduce chaos. The goal is to observe, monitor, respond to, and improve the reliability of your system under adverse conditions.
Read more here.