edit pass: vminsights-troubleshoot

Author: ShawnJackson

articles/azure-monitor/vm/vminsights-troubleshoot.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshoot VM insights
-description: Get troubleshooting information for installation of VM insights.
+description: Get troubleshooting information about agent installation and the use of VM insights in Azure Monitor.
 ms.topic: conceptual
 author: guywi-ms
 ms.author: guywild
@@ -18,12 +18,12 @@ This article provides troubleshooting information to help you with problems that
 When you onboard an Azure virtual machine from the Azure portal, the following actions occur:
 
 - A default Log Analytics workspace is created if you selected that option.
-- The Azure Monitor Agent is installed on Azure virtual machines through a VM extension, if the agent is already installed.
-- The Dependency Agent is installed on Azure virtual machines through an extension, if it's required.
+- The Azure Monitor Agent is installed on the virtual machine through an extension, if the agent is already installed.
+- The Dependency Agent is installed on the virtual machine through an extension, if it's required.
 
 During the onboarding process, each of these steps is verified and a notification status appears in the portal. Configuration of the workspace and the agent installation typically takes 5 to 10 minutes. It takes another 5 to 10 minutes for data to become available to view in the portal.
 
-If you receive a message that the virtual machine needs to be onboarded after you perform the onboarding process, allow up to 30 minutes for the process to finish. If the issue persists, see the following sections for possible causes.
+If you receive a message that the virtual machine needs to be onboarded after you perform the onboarding process, allow up to 30 minutes for the process to finish. If the problem persists, see the following sections for possible causes.
 
 ### Is the virtual machine running?
 
@@ -34,11 +34,11 @@ If the virtual machine has been turned off for a while, is off currently, or was
 If the operating system isn't in the [list of supported operating systems](vminsights-enable-overview.md#supported-operating-systems), installation of the extension fails and you get a message about waiting for data to arrive.
 
 > [!IMPORTANT]
-> As of April 11, 2022, if your virtual machine doesn't appear in VM insights, you might be running an older version of the Dependency Agent. For more information, see the blog post [Potential breaking changes for VM insights Linux customers](https://techcommunity.microsoft.com/t5/azure-monitor-status/potential-breaking-changes-for-vm-insights-linux-customers/ba-p/3271989). This consideration doesn't apply for Windows machines and for VMs that you onboarded before April 11, 2022.
+> If a virtual machine that you onboarded on or after April 11, 2022, doesn't appear in VM insights, you might be running an older version of the Dependency Agent. For more information, see the blog post [Potential breaking changes for VM insights Linux customers](https://techcommunity.microsoft.com/t5/azure-monitor-status/potential-breaking-changes-for-vm-insights-linux-customers/ba-p/3271989). This consideration doesn't apply for Windows machines and for virtual machines that you onboarded before April 11, 2022.
 
 ### Was the extension installed properly?
 
-If you still see a message that the virtual machine needs to be onboarded, it might mean that one or both of the extensions failed to be installed correctly. In the Azure portal, on the **Extensions** pane for your virtual machine, check whether the following extensions appear.
+If you still see a message that the virtual machine needs to be onboarded, it might mean that one or both of the extensions failed to be installed correctly. In the Azure portal, on the **Extensions** pane for your virtual machine, check whether the following extensions appear:
 
 | Operating system | Agents |
 |:---|:---|
@@ -47,119 +47,120 @@ If you still see a message that the virtual machine needs to be onboarded, it mi
 
 If you don't see both extensions for your operating system in the list of installed extensions, you must install them. If the extensions are listed but their status doesn't appear as **Provisioning succeeded**, remove the extensions and reinstall them.
 
-### Do you have connectivity issues?
+### Do you have connectivity problems?
 
-For Windows machines, you can use the TestCloudConnectivity tool to identify the connectivity issue. This tool is installed by default with the agent in the folder *%SystemDrive%\Program Files\Microsoft Monitoring Agent\Agent*. Run the tool from an elevated command prompt. It returns results and highlights where the test fails.
+For Windows machines, you can use the TestCloudConnectivity tool to identify a connectivity problem. This tool is installed by default with the agent in the folder *%SystemDrive%\Program Files\Microsoft Monitoring Agent\Agent*.
 
-:::image type="content" source="media/vminsights-troubleshoot/test-cloud-connectivity.png" lightbox="media/vminsights-troubleshoot/test-cloud-connectivity.png" alt-text="Screenshot that shows the tool for testing cloud connectivity." border="false":::
+Run the tool from an elevated command prompt. It returns results and highlights where the test fails.
 
-## DCR created by the VM insights process was modified and now data is missing
+:::image type="content" source="media/vminsights-troubleshoot/test-cloud-connectivity.png" lightbox="media/vminsights-troubleshoot/test-cloud-connectivity.png" alt-text="Screenshot that shows the tool for testing cloud connectivity.":::
 
-### Identify the issue
+## DCR created by the VM insights process was modified and now data is missing
 
-To identify whether a data collection rule (DCR) was modified:
+### Identify the problem
 
-1. Go to the Azure Monitor dashboard.
-1. Locate the DCR.
-1. View the JSON properties by using the **JSON View** link on the upper-right side of the overview pane.
+To identify whether a data collection rule (DCR) was modified, go to the Azure Monitor dashboard and locate the DCR. View the JSON properties by using the **JSON View** link on the upper-right side of the overview pane.
 
-   ![Screenshot of JSON for a data collection rule.](media/vminsights-troubleshoot/dcr-overview.png)
+:::image type="content" source="media/vminsights-troubleshoot/dcr-overview.png" lightbox="media/vminsights-troubleshoot/dcr-overview.png" alt-text="Screenshot of JSON for a data collection rule.":::
 
-   In this example, the original stream name was changed to reflect the name of the performance counter stream.
+In this example, the original stream name was changed to reflect the name of the performance counter stream.
 
-   ![Screenshot that shows a changed stream name in a data collection rule.](media/vminsights-troubleshoot/dcr-json.png)
+:::image type="content" source="media/vminsights-troubleshoot/dcr-json.png" lightbox="media/vminsights-troubleshoot/dcr-json.png" alt-text="Screenshot that shows a changed stream name in a data collection rule.":::
 
-   Although the counter sections are pointing the `perf` table, the stream dataflow is still configured for the proper destination `Microsoft-InsightsMetrics`.
+Although the counter sections are pointing the `perf` table, the stream dataflow is still configured for the proper destination `Microsoft-InsightsMetrics`.
 
-### Resolve the issue
+### Resolve the problem
 
-You can't resolve this issue by using the Azure Monitor dashboard directly. But you can resolve it by exporting the template, normalizing the name, and then importing the modified rule over itself.
+You can't resolve this problem by using the Azure Monitor dashboard directly. But you can resolve it by exporting the template, normalizing the name, and then importing the modified rule over itself.
 
 #### Export the DCR and save locally
 
 1. On the Azure Monitor dashboard, go to the DCR.
 
 2. Select **Export template**.
 
-   ![Screenshot of the menu option to export a template for a data collection rule.](media/vminsights-troubleshoot/dcr-export.png)
+   :::image type="content" source="media/vminsights-troubleshoot/dcr-export.png" lightbox="media/vminsights-troubleshoot/dcr-export.png" alt-text="Screenshot of the menu option to export a template for a data collection rule.":::
 
 3. On the **Export template** pane for the selected DCR, the portal creates the template file and a matching parameter file. After this process is complete, select **Download** to download the template package and save it locally.
 
-   ![Screenshot of the button for downloading a template for a data collection rule.](media/vminsights-troubleshoot/template-download.png)
+   :::image type="content" source="media/vminsights-troubleshoot/template-download.png" lightbox="media/vminsights-troubleshoot/template-download.png" alt-text="Screenshot of the button for downloading a template for a data collection rule.":::
 
 4. Select **Open file**.
 
-   ![Screenshot that shows the link for opening a downloaded file package.](media/vminsights-troubleshoot/downloads.png)
+   :::image type="content" source="media/vminsights-troubleshoot/downloads.png" lightbox="media/vminsights-troubleshoot/downloads.png" alt-text="Screenshot that shows the link for opening a downloaded file package.":::
 
 5. Copy the two .json files to a local folder.
 
-   ![Screenshot that shows parameter and template files copied to a local folder.](media/vminsights-troubleshoot/copy-file.png)
+   :::image type="content" source="media/vminsights-troubleshoot/copy-file.png" lightbox="media/vminsights-troubleshoot/copy-file.png" alt-text="Screenshot that shows parameter and template files copied to a local folder.":::
 
 #### Modify the template
 
 1. Open the template file in the editor of your choice. Then locate the invalid stream name under the performance counter data source.
 
-   ![Screenshot of a template file.](media/vminsights-troubleshoot/update-template.png)
+   :::image type="content" source="media/vminsights-troubleshoot/update-template.png" lightbox="media/vminsights-troubleshoot/update-template.png" alt-text="Screenshot of a template file.":::
 
-2. Using the valid stream name from the dataflow node, fix the invalid reference. Then save and close your file.
+2. By using the valid stream name from the dataflow node, fix the invalid reference. Then save and close your file.
 
-   ![Screenshot of an updated stream name in a template file.](media/vminsights-troubleshoot/correct-template.png)
+   :::image type="content" source="media/vminsights-troubleshoot/correct-template.png" lightbox="media/vminsights-troubleshoot/correct-template.png" alt-text="Screenshot of an updated stream name in a template file.":::
 
 #### Import the template by using the custom deployment feature
 
 1. Back in the portal, search for and then select **Deploy a custom template**.
 
-   ![Screenshot of search results for the service that deploys a custom template.](media/vminsights-troubleshoot/deploy-template.png)
+   :::image type="content" source="media/vminsights-troubleshoot/deploy-template.png" lightbox="media/vminsights-troubleshoot/deploy-template.png" alt-text="Screenshot of search results for the service that deploys a custom template.":::
 
 2. On the **Custom deployment** pane, select **Build your own template in the editor**.
 
-   ![Screenshot of the option to build your own template in the editor.](media/vminsights-troubleshoot/build-template.png)
+   :::image type="content" source="media/vminsights-troubleshoot/build-template.png" lightbox="media/vminsights-troubleshoot/build-template.png" alt-text="Screenshot of the option to build your own template in the editor.":::
 
-3. Select **Load file**, and then browse to your saved template and parameter file.
+3. Select **Load file**, and then browse to your saved template and parameter files.
 
-   ![Screenshot of Load File.](media/vminsights-troubleshoot/load-file.png)
+   :::image type="content" source="media/vminsights-troubleshoot/load-file.png" lightbox="media/vminsights-troubleshoot/load-file.png" alt-text="Screenshot of the button for loading a file.":::
 
-4. Visually inspect the template to validate the change is in place and select the Save button.
+4. Visually inspect the template to validate that the change is in place, and then select **Save**.
 
-   ![Screenshot of Edit Template.](media/vminsights-troubleshoot/save-template.png)
+   :::image type="content" source="media/vminsights-troubleshoot/save-template.png" lightbox="media/vminsights-troubleshoot/save-template.png" alt-text="Screenshot of the pane for editing a template.":::
 
-5. From here the portal will use the parameter file to fill in the deployment options (which can be changed) or left intact to overwrite the existing DCR, Once completed select the review and Create button.
+5. The portal uses the parameter file to fill in the deployment options (which can be changed or left intact to overwrite the existing DCR). When the portal completes the process, select the **Review + create** button.
 
-   ![Screenshot of Custom Deployment.](media/vminsights-troubleshoot/deploy.png)
+   :::image type="content" source="media/vminsights-troubleshoot/deploy.png" lightbox="media/vminsights-troubleshoot/deploy.png" alt-text="Screenshot of the pane for custom deployment.":::
 
-6. After validation then we can select the Create button to finalize the deployment.
+6. After validation, select **Create** to finish the deployment.
 
-   ![Screenshot of Create Deployment.](media/vminsights-troubleshoot/create-deployment.png)
+   :::image type="content" source="media/vminsights-troubleshoot/create-deployment.png" lightbox="media/vminsights-troubleshoot/create-deployment.png" alt-text="Screenshot of the button for creating a custom deployment.":::
 
-7. After the deployment is complete, we can browse to the DCR again and review the JSON in overview blade:
+7. After the deployment is complete, browse to the DCR again and review the JSON in the overview pane.
 
-   ![Screenshot of Review JSON.](media/vminsights-troubleshoot/updated-json.png)
+   :::image type="content" source="media/vminsights-troubleshoot/updated-json.png" lightbox="media/vminsights-troubleshoot/updated-json.png" alt-text="Screenshot of the pane for reviewing JSON.":::
 
-8. The agent will detect this change and download the new configuration, and this should restore ingestion to the insight metrics table.
+8. The agent detects the change and downloads the new configuration, which restores ingestion to the `Microsoft-InsightsMetrics` table.
 
 ## Performance view has no data
 
-If the agents appear to be installed correctly but you don't see any data in the **Performance** view, see the following sections for possible causes.
+If the agents appear to be installed correctly but no data appears in the **Performance** view, see the following sections for possible causes.
 
 ### Has your Log Analytics workspace reached its data limit?
 
 Check the [capacity reservations and the pricing for data ingestion](https://azure.microsoft.com/pricing/details/monitor/).
 
 ### Is your virtual machine agent connected to Azure Monitor Logs?
 
-Open Log Analytics from **Logs** in the Azure Monitor menu in the Azure portal. Run the following query for your computer:
+In the Azure portal, on the **Azure Monitor** menu, select **Logs** to open the Log Analytics workspace. Run the following query for your computer:
 
 ```kusto
 Heartbeat
 | where Computer == "my-computer"
 | sort by TimeGenerated desc 
 ```
 
-If you don't see any data or if the computer hasn't sent a heartbeat recently, you might have problems with your agent. See the preceding section for agent troubleshooting information.
+If no data appears or if the computer didn't send a heartbeat recently, you might have problems with your agent. For agent troubleshooting information, see these articles:
+
+- [Troubleshoot issues with the Log Analytics agent for Windows](../agents/agent-windows-troubleshoot.md)
+- [Troubleshoot issues with the Log Analytics agent for Linux](../agents/agent-linux-troubleshoot.md)
 
 ## Virtual machine doesn't appear in the Map view
 
-See the following sections for issues with the **Map** view.
+The following sections help you resolve problems with the **Map** view.
 
 ### Is the Dependency Agent installed?
 
@@ -171,11 +172,11 @@ The [Log Analytics free tier](https://azure.microsoft.com/pricing/details/monito
 
 ### Is your virtual machine sending log and performance data to Azure Monitor Logs?
 
-Use the log query in the [Performance view has no data](#performance-view-has-no-data) section to determine if data is being collected for the virtual machine. If no data is being collected, use the TestCloudConnectivity tool to determine if you have connectivity issues.
+Use the log query in the [Performance view has no data](#performance-view-has-no-data) section to determine if data is being collected for the virtual machine. If no data is being collected, use the TestCloudConnectivity tool to determine if you have connectivity problems.
 
 ## Virtual machine appears in the Map view but has missing data
 
-If the virtual machine is in the **Map** view, the Dependency Agent is installed and running, but the kernel driver didn't load, check the log file at the following locations:
+If the virtual machine is in the **Map** view and the Dependency Agent is installed and running, but the kernel driver didn't load, check the log file at the following locations:
 
 | Operating system | Log |
 |:---|:---|
@@ -186,6 +187,4 @@ The last lines of the file should indicate why the kernel didn't load. For examp
 
 ## Related content
 
-- [Enable VM insights overview](vminsights-enable-overview.md).
-- [Troubleshoot issues with the Log Analytics agent for Windows](../agents/agent-windows-troubleshoot.md)
-- [Troubleshoot issues with the Log Analytics agent for Linux](../agents/agent-linux-troubleshoot.md)
+- For more information about installing VM insights agents, see [Enable VM insights overview](vminsights-enable-overview.md)