Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Experiments (classic) is being replaced by Chaos Studio Workspaces, the current resource model for Azure Chaos Studio. It's still Chaos Studio, with a new way to define and run your tests. Microsoft no longer adds features to Experiments (classic) and considers only critical fixes, such as security updates, for backport to this model. Use Workspaces for new resilience tests. To move your existing experiments, follow Move from Experiments (classic) to Chaos Studio Workspaces.
These diagnostic settings emit telemetry for Azure Chaos Studio Experiments (classic). For current-model tests, use Chaos Studio Scenario reports to review Actions and timing, then correlate the run with resource and application monitoring.
In this guide, we'll show you the steps needed to integrate an Experiment to emit telemetry to Azure Monitor. These events show the start and stop of each fault as well as the type of fault executed and the resource the fault was executed against. You can overlay this data on top of your existing Azure Monitor or external monitoring dashboards.
Prerequisites
- An Azure subscription
- An existing Chaos Studio Experiment How to create your first Chaos Experiment
- An existing Log Analytics Workspace How to Create a Log Analytics Workspace
Step 1: Navigate to Diagnostic Settings tab in your Chaos Experiment
Navigate to the Chaos Experiment you want to emit telemetry to Azure Monitor and open it. Then navigate to the "Diagnostic settings" tab under the "Monitoring" section as shown in the below screenshot:
Step 2: Connect your Chaos Experiment to your desired Log Analytics Workspace
Once you are in the "Diagnostic Settings" tab within your Chaos Experiment, select "Add Diagnostic Setting." Enter the following details:
- Diagnostic Setting Name: Any String you want, much like a Resource Group Name
- Category Groups:Choose which category of logging you want to output to the Log Analytics workspace.
- Subscription: The subscription which includes the Log Analytics Workspace you would like to use
- Log Analytics Workspace: Where you'll select your desired Log Analytics Workspace
All the other settings are optional
Step 3: Run the chaos experiment
Once you have completed Step 2, your experiment is now configured to emit telemetry to Azure Monitor upon the next Chaos Experiment execution! It typically takes time (20 minutes) for the logs to populate. Once populated you can view the log events from the logs tab. Events include experiment start, stop, and details about the faults executed. You can even turn the logs into chart visualizations or overlay your existing live site visualizations with chaos metadata.
To query your logs, navigate to the "Logs" tab in your Chaos Experiment Resource to get your desired logging information in your desired format.
