Azure Monitor diagnostic extension configure in portal

Author: bwren

articles/azure-monitor/platform/diagnostics-extension-overview.md

@@ -15,6 +15,14 @@ Azure Diagnostics extension is an [agent in Azure Monitor](agents-overview.md) t
 > [!NOTE]
 > Azure Diagnostics extension is one of the agents available to collect monitoring data from the guest operating system of compute resources. See [Overview of the Azure Monitor agents ](agents-overview.md) for a description of the different agents and guidance on selecting the appropriate agents for your requirements.
 
+## Primary scenarios
+The primary scenarios addressed by the diagnostics extension are:
+
+- Collect guest metrics into Azure Monitor Metrics.
+- Send guest logs and metrics to Azure storage for archiving.
+- Send guest logs and metrics to Azure event hubs to send outside of Azure.
+
+
 ## Comparison to Log Analytics agent
 The Log Analytics agent in Azure Monitor can also be used to collect monitoring data from the guest operating system of virtual machines. You may choose to use either or both depending on your requirements. See [Overview of the Azure Monitor agents](agents-overview.md) for a detailed comparison of the Azure Monitor agents. 
 

articles/azure-monitor/platform/diagnostics-extension-windows-install.md

@@ -10,35 +10,58 @@ ms.date: 02/17/2020
 ms.author: bwren
 ---
 # Install and configure Windows Azure diagnostics extension (WAD)
-Azure diagnostics extension is an agent in Azure Monitor that collects monitoring data from the guest operating system and workloads of Azure virtual machines and other compute resources. This article provides details on installing and configuring the Windows diagnostics extension and a description of how the data is stored in and Azure Storage account.
+[Azure diagnostics extension](diagnostics-extension-overview.md) is an agent in Azure Monitor that collects monitoring data from the guest operating system and workloads of Azure virtual machines and other compute resources. This article provides details on installing and configuring the Windows diagnostics extension and a description of how the data is stored in and Azure Storage account.
 
 The diagnostics extension is implemented as a [virtual machine extension](../../virtual-machines/extensions/overview.md) in Azure, so it supports the same installation options using Resource Manager templates, PowerShell, and CLI. See [Virtual machine extensions and features for Windows](../../virtual-machines/extensions/features-windows.md) for details on installing and maintaining virtual machine extensions.
 
+## Overview
+When you configure Windows Azure the diagnostics extension, you must specify a storage account where all specified data will be sent. You can optionally add one for more *data sinks* to send the data to different locations.
+
+- Azure Monitor sink - Send guest performance data to Azure Monitor Metrics.
+- Event hub sink - Send guest performance and log data to Azure event hubs to forward outside of Azure. This sink cannot be configured in the Azure portal.
+
+
 ## Install with Azure portal
 You can install and configure the diagnostics extension on an individual virtual machine in the Azure portal which provides you an interface as opposed to working directly with the configuration. When you enable the diagnostics extension, it will automatically use a default configuration with the most common performance counters and events. You can modify this default configuration according to your specific requirements.
 
 > [!NOTE]
-> There are diagnostics extension settings you cannot configure using the Azure portal including sending data to Azure Event Hubs. You must use one of the other configuration methods for these settings.
+> The following describe the most common settings for the diagnostics extension. For details on all of the configuration options, see [Windows diagnostics extension schema](diagnostics-extension-schema-windows).
 
 1. Open the menu for a virtual machine in the Azure portal.
 2. Click on **Diagnostic settings** in the **Monitoring** section of the VM menu.
 3. Click **Enable guest-level monitoring** if the diagnostics extension hasn't already been enabled.
-4. A new Azure Storage account will be created for the VM with the name will be based on the name of the resource group for the VM. You can attach the VM to another storage account by selecting the **Agent** tab.
 
-![Diagnostic settings](media/diagnostics-extension-windows-install/diagnostic-settings.png)
+  ![Enable monitoring](media/diagnostics-extension-windows-install/enable-monitoring.png)
+
+4. A new Azure Storage account will be created for the VM with the name will be based on the name of the resource group for the VM, and a default set of guest performance counters and logs will be selected.
+
+  ![Diagnostic settings](media/diagnostics-extension-windows-install/diagnostic-settings.png)
+
+5. In the **Performance counters** tab, select the guest metrics you would like to collect from this virtual machine. Use the **Custom** setting for more advanced selection.
+
+  ![Performance counters](media/diagnostics-extension-windows-install/performance-counters.png)
+
+6. In the **Logs** tab, select the logs to collect from the virtual machine. Logs can be sent to storage or event hubs, but not to Azure Monitor. Use the [Log Analytics agent](log-analytics-agent.md) to collect guest logs to Azure Monitor.
+
+  ![Logs](media/diagnostics-extension-windows-install/logs.png)
+
+7. In the **Crash dumps** tab, specify any processes to collect memory dumps after a crash. The data will be written to the storage account for the diagnostic setting, and you can optionally specify a blob container.
+   
+  ![Crash dumps](media/diagnostics-extension-windows-install/crash-dumps.png)
+
+8. In the **Sinks** tab, specify whether to send the data to locations other than Azure storage. If you select **Azure Monitor**, guest performance data will be sent to Azure Monitor Metrics. You cannot configure the event hubs sink using the Azure portal.
+
+  ![Sinks](media/diagnostics-extension-windows-install/sinks.png)
+
+  If you have not enabled a System Assigned Identity configured for your your virtual machine, you may see the below warning when you save a configuration with the Azure Monitor sink. Click on the banner to enable the system assigned identity.
 
+  ![Managed entity](media/diagnostics-extension-windows-install/managed-entity.png)
 
-You can modify the default configuration once the diagnostics extension has been enabled. The following table describes the options you can modify in the different tabs. Some options have a **Custom** command which allows you to specify more detailed configuration; see [Windows diagnostics extension schema](diagnostics-extension-schema-windows.md) for details on different settings.
+9. In the **Agent**, you can change the storage account, set the disk quota, and specifygy whether to collect diagnostic infrastructure logs.  
 
-| Tab | Description |
-|:---|:---|
-| Overview | Displays the current configuration with links to the other tabs. |
-| Performance counters | Select the performance counters to collect and the sample rate for each.  |
-| Logs | Select the log data to collect. This includes Windows Event logs, IIS logs, .NET application logs and ETW events.  |
-| Crash dumps | Enable crash dump for different processes. |
-| Sinks | Enable data sinks to send data to destinations in addition to Azure Storage.<br>Azure Monitor - Sends performance data to Azure Monitor Metrics.<br>Application Insights - Send data to an Application Insights application. |
-| Agent | Modify the following configuration for the agent:<br>- Change the storage account.<br>- Specify the maximum local disk used for the agent.<br>- Configure logs for the health of the agent itself.|
+  ![Agent](media/diagnostics-extension-windows-install/agent.png)
 
+10. Click **Save** to save the configuration. 
 
 > [!NOTE]
 > While the configuration for diagnostics extension can be formatted in either JSON or XML, any configuration done in the Azure portal will always be stored as JSON. If you use XML with another configuration method and then change your configuration with the Azure portal, the settings will be changed to JSON.