Merge pull request #253216 from nikhilkaul-msft/main

Chaos Studio Add AppInsights and AzureMonitor Set Up Docs

Author: American-Dipper

articles/chaos-studio/TOC.yml

@@ -74,6 +74,10 @@
       href: chaos-studio-tutorial-dynamic-target-cli.md
   - name: Troubleshoot common issues
     href: troubleshooting.md
+  - name: Set up your Chaos Experiment to emit telemetry to Azure Monitor
+    href: chaos-studio-set-up-azure-monitor.md
+  - name: Set up your Agent-Based Chaos Experiment to emit telemetry to App Insights
+    href: chaos-studio-set-up-app-insights.md
 - name: Reference
   items:
   - name: Fault library

articles/chaos-studio/chaos-studio-set-up-app-insights.md

@@ -0,0 +1,53 @@
+---
+title: Set up App Insights for a Chaos Studio agent-based experiment
+description: Understand the steps to connect App Insights to your Chaos Studio Agent-Based Experiment
+services: chaos-studio
+author: nikhilkaul-msft
+ms.topic: how-to
+ms.date: 09/27/2023
+ms.author: nikhilkaul
+ms.service: chaos-studio
+ms.custom: ignite-fall-2023
+---
+# How-to: Configure your experiment to emit Experiment Fault Events to App Insights
+In this guide, we'll show you the steps needed to configure a Chaos Studio **Agent-based** Experiment to emit telemetry to App Insights. 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. App Insights is the primary recommended logging solution for **Agent-based** experiments in Chaos Studio.
+
+## Prerequisites
+- An Azure subscription
+- An existing Chaos Studio [**Agent-based** Experiment](chaos-studio-tutorial-agent-based-portal.md)
+- [Required for Application Insights Resource as well] An existing [Log Analytics Workspace](../azure-monitor/logs/quick-create-workspace.md)
+- An existing [Application Insights Resource](../azure-monitor/app/create-workspace-resource.md)
+- [Required for Agent-based Chaos Experiments] A [User-Assigned Managed Identity](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md)
+
+## Step 1: Copy the Instrumentation Key from your Application Insights Resource
+Once you have met all the prerequisite steps, copy the **Instrumentation Key** found in the overview page of your Application Insights Resource (see screenshot)
+
+<br/>
+
+[![Screenshot that shows Instrumentation Key in App Insights.](images/step-1a-app-insights.png)](images/step-1a-app-insights.png#lightbox)
+
+## Step 2: Enable the Target Platform for your Agent-Based Fault with Application Insights
+Navigate to the Chaos Studio overview page and click on the **Targets** blade under the "Experiments Management" section. Find the target platform, ensure it's enabled for agent-based faults, and select "Manage Actions" in the right-most column. See screenshot below for an example:
+<br/>
+
+<br/>
+
+[![Screenshot that shows the Chaos Targets Page.](images/step-2a-app-insights.png)](images/step-2a-app-insights.png#lightbox)
+
+## Step 3: Add your Application Insights account and Instrumentation key
+At this point, the resource configuration page seen in the screenshot should come up . After configuring your managed identity, make sure Application Insights is "Enabled" and then select your desired Application Insights Account and enter the Instrumentation Key you copied in Step 1. Once you have filled out the required information, you can click "Review+Create" to deploy your resource. 
+
+<br/>
+
+[![Screenshot of Targets Deployment Page.](images/step-3a-app-insights.png)](images/step-3a-app-insights.png#lightbox)
+
+## Step 4: Run the chaos experiment
+At this point, your Chaos Target is now configured to emit telemetry to the App Insights Resource you configured! If you navigate to your specific Application Insights Resource and open the "Logs" blade under the "Monitoring" section, you should see the Agent health status and any actions the Agent is taking on your Target Platform. You can now run your experiment and see logging in your Application Insights Resource. See screenshot for example of App Insights Resource running successfully on an Agent-based Chaos Target platform. 
+
+<br/>
+
+To query your logs, navigate to the "Logs" tab in the Application Insights Resource to get your desired logging information your desired format.
+
+<br/>
+
+[![Screenshot of Logs tab in Application Insights Resource.](images/step-4a-app-insights.png)](images/step-4a-app-insights.png#lightbox)

articles/chaos-studio/chaos-studio-set-up-azure-monitor.md

@@ -0,0 +1,51 @@
+---
+title: Set up Azure monitor for a Chaos Studio experiment
+description: Understand the steps to connect Azure Monitor to your Chaos Studio Experiment
+services: chaos-studio
+author: nikhilkaul-msft
+ms.topic: how-to
+ms.date: 09/27/2023
+ms.author: nikhilkaul
+ms.service: chaos-studio
+ms.custom: ignite-fall-2023
+---
+# How-to: Configure your experiment to emit Experiment Fault Events to Azure Monitor
+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](chaos-studio-quickstart-azure-portal.md)
+- An existing Log Analytics Workspace [How to Create a Log Analytics Workspace](../azure-monitor/logs/quick-create-workspace.md)
+
+## 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:
+
+<br/>
+
+[![Screenshot that shows Diagnostic Settings in Chaos Experiment.](images/step-1a.png)](images/step-1a.png#lightbox)
+
+## 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:
+1. **Diagnostic Setting Name**: Any String you want, much like a Resource Group Name
+2. **Category Groups**:Choose which category of logging you want to output to the Log Analytics workspace. 
+3. **Subscription**: The subscription which includes the Log Analytics Workspace you would like to use
+4. **Log Analytics Workspace**: Where you'll select your desired Log Analytics Workspace
+<br/>
+All the other settings are optional
+<br/>
+
+<br/>
+
+[![Screenshot that shows the Diagnostic Settings blade and required information.](images/step-2a.png)](images/step-2a.png#lightbox)
+
+## 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.
+
+<br/>
+
+To query your logs, navigate to the "Logs" tab in your Chaos Experiment Resource to get your desired logging information in your desired format.
+
+<br/>
+
+[![Screenshot of Logs tab in Chaos Experiment Resource.](images/step-3a.png)](images/step-3a.png#lightbox)