Merge pull request #234926 from paulth1/virtual-machines-batch-5

[AQ] edit pass: Virtual machines batch 5

Author: ShawnJackson

articles/azure-monitor/best-practices-cost.md

@@ -54,7 +54,7 @@ This article describes [Cost optimization](/azure/architecture/framework/cost/)
 
 | Recommendation | Benefit |
 |:---|:---|
-| Configure VM agents to collect only important events. | Virtual machines can vary significantly in the amount of data they collect, depending on the amount of telemetry generated by the applications and services they have installed. See [Monitor virtual machines with Azure Monitor: Workloads](vm/monitor-virtual-machine-data-collection.md#controlling-costs) for guidance on data to collect and strategies for using [XPath queries](agents/data-collection-rule-azure-monitor-agent.md#filter-events-using-xpath-queries) to limit it.|
+| Configure VM agents to collect only important events. | Virtual machines can vary significantly in the amount of data they collect, depending on the amount of telemetry generated by the applications and services they have installed. See [Monitor virtual machines with Azure Monitor: Workloads](vm/monitor-virtual-machine-data-collection.md#control-costs) for guidance on data to collect and strategies for using [XPath queries](agents/data-collection-rule-azure-monitor-agent.md#filter-events-using-xpath-queries) to limit it.|
 | Ensure that VMs aren't sending duplicate data. | Any configuration that uses multiple agents on a single machine or where you multi-home agents to send data to multiple workspaces may incur charges for the same data multiple times. If you do multi-home agents, make sure you're sending unique data to each workspace. See [Analyze usage in Log Analytics workspace](logs/analyze-usage.md) for guidance on analyzing your collected data to make sure you aren't collecting duplicate data. If you're migrating between agents, continue to use the Log Analytics agent until you [migrate to the Azure Monitor agent](./agents/azure-monitor-agent-migration.md) rather than using both together unless you can ensure that each is collecting unique data. |
 | Use transformations to filter unnecessary data from collected events. | [Transformations](essentials/data-collection-transformations.md) can be used in data collection rules to remove unnecessary data or even entire columns from events collected from the virtual machine which can significantly reduce the cost for their ingestion and retention. |
 

articles/azure-monitor/vm/monitor-virtual-machine-data-collection.md

@@ -11,31 +11,29 @@ ms.date: 06/08/2022
 # Enable VM insights for a hybrid virtual machine
 This article describes how to enable VM insights for a virtual machine outside of Azure, including on-premises and other cloud environments.
 
-> [!IMPORTANT]
-> The recommended method of enabling hybrid VMs is first enabling [Azure Arc for servers](../../azure-arc/servers/overview.md) so that the VMs can be enabled for VM insights using processes similar to Azure VMs. This article describes how to onboard hybrid VMs if you choose not to use Azure Arc.
+To enable hybrid VMs, first enable [Azure Arc for servers](../../azure-arc/servers/overview.md) so that the VMs can be enabled for VM insights by using processes similar to Azure VMs. This article describes how to onboard hybrid VMs if you choose not to use Azure Arc.
 
 [!INCLUDE [monitoring-limits](../../../includes/azure-monitor-vminsights-agent.md)]
 
-
 ## Prerequisites
 
 - [Create and configure a Log Analytics workspace](./vminsights-configure-workspace.md).
-- See [Supported operating systems](./vminsights-enable-overview.md#supported-operating-systems) to ensure that the operating system of the virtual machine or virtual machine scale set you're enabling is supported. 
-
+- See [Supported operating systems](./vminsights-enable-overview.md#supported-operating-systems) to ensure that the operating system of the virtual machine or virtual machine scale set you're enabling is supported.
 
 ## Overview
-Virtual machines outside of Azure require the same Log Analytics agent and Dependency agent that are used for Azure VMs. Since you can't use VM extensions to install the agents though, you must manually install them in the guest operating system or have them installed through some other method. 
+Virtual machines outside of Azure require the same Log Analytics agent and Dependency agent that are used for Azure VMs. Because you can't use VM extensions to install the agents, you must manually install them in the guest operating system or have them installed through some other method.
 
-See [Connect Windows computers to Azure Monitor](../agents/agent-windows.md) or [Connect Linux computers to Azure Monitor](../agents/agent-linux.md) for details on deploying the Log Analytics agent. Details for the Dependency agent are provided in this article. 
+For information on how to deploy the Log Analytics agent, see [Connect Windows computers to Azure Monitor](../agents/agent-windows.md) or [Connect Linux computers to Azure Monitor](../agents/agent-linux.md). Details for the Dependency agent are provided in this article.
 
 ## Firewall requirements
-Firewall requirements for the Log Analytics agent are provided in [Log Analytics agent overview](../agents/log-analytics-agent.md#network-requirements). The VM insights Map Dependency agent doesn't transmit any data itself, and it doesn't require any changes to firewalls or ports. The Map data is always transmitted by the Log Analytics agent to the Azure Monitor service, either directly or through the [Operations Management Suite gateway](../../azure-monitor/agents/gateway.md) if your IT security policies don't allow computers on the network to connect to the internet.
+Firewall requirements for the Log Analytics agent are provided in [Log Analytics agent overview](../agents/log-analytics-agent.md#network-requirements). The VM insights Map Dependency agent doesn't transmit any data itself, and it doesn't require any changes to firewalls or ports.
 
+The Map data is always transmitted by the Log Analytics agent to the Azure Monitor service. Data is transmitted either directly or through the [Operations Management Suite gateway](../../azure-monitor/agents/gateway.md) if your IT security policies don't allow computers on the network to connect to the internet.
 
 ## Dependency agent
 
 >[!NOTE]
->The following information described in this section is also applicable to the [Service Map solution](./service-map.md).  
+>The following information described in this section also applies to the [Service Map solution](./service-map.md).
 
 You can download the Dependency agent from these locations:
 
@@ -44,10 +42,9 @@ You can download the Dependency agent from these locations:
 | [InstallDependencyAgent-Windows.exe](https://aka.ms/dependencyagentwindows) | Windows | 9.10.16.22650 | BE537D4396625ADD93B8C1D5AF098AE9D9472D8A20B2682B32920C5517F1C041    |
 | [InstallDependencyAgent-Linux64.bin](https://aka.ms/dependencyagentlinux) | Linux | 9.10.16.22650 | FF86D821BA845833C9FE5F6D5C8A5F7A60617D3AD7D84C75143F3E244ABAAB74  |
 
-
 ## Install the Dependency agent on Windows
 
-You can install the Dependency agent manually on Windows computers by running `InstallDependencyAgent-Windows.exe`. If you run this executable file without any options, it starts a setup wizard that you can follow to install the agent interactively. You require *Administrator* privileges on the guest OS to install or uninstall the agent.
+You can install the Dependency agent manually on Windows computers by running `InstallDependencyAgent-Windows.exe`. If you run this executable file without any options, it starts a setup wizard that you can follow to install the agent interactively. You require Administrator privileges on the guest OS to install or uninstall the agent.
 
 The following table highlights the parameters that are supported by setup for the agent from the command line.
 
@@ -69,7 +66,6 @@ Invoke-WebRequest "https://aka.ms/dependencyagentwindows" -OutFile InstallDepend
 .\InstallDependencyAgent-Windows.exe /S
 ```
 
-
 ## Install the Dependency agent on Linux
 
 The Dependency agent is installed on Linux servers from *InstallDependencyAgent-Linux64.bin*, a shell script with a self-extracting binary. You can run the file by using `sh` or add execute permissions to the file itself.
@@ -98,7 +94,7 @@ Files for the Dependency agent are placed in the following directories:
 | Service executable files | /opt/microsoft/dependency-agent/bin/microsoft-dependency-agent<br>/opt/microsoft/dependency-agent/bin/microsoft-dependency-agent-manager |
 | Binary storage files | /var/opt/microsoft/dependency-agent/storage |
 
-### Shell script 
+### Shell script
 Use the following sample shell script to download and install the agent:
 
 ```
@@ -108,7 +104,7 @@ sudo sh InstallDependencyAgent-Linux64.bin -s
 
 ## Desired State Configuration
 
-To deploy the Dependency agent using Desired State Configuration (DSC), you can use the xPSDesiredStateConfiguration module with the following example code:
+To deploy the Dependency agent by using Desired State Configuration (DSC), you can use the `xPSDesiredStateConfiguration` module with the following example code:
 
 ```powershell
 configuration VMInsights {
@@ -142,41 +138,38 @@ configuration VMInsights {
 }
 ```
 
-
-
 ## Troubleshooting
 
-### VM doesn't appear on the map
+This section offers troubleshooting tips for common issues.
 
-If your Dependency agent installation succeeded, but you don't see your computer on the map, diagnose the problem by following these steps.
+### VM doesn't appear on the map
 
-1. Is the Dependency agent installed successfully? You can validate this by checking to see if the service is installed and running.
+If your Dependency agent installation succeeded but you don't see your computer on the map, diagnose the problem by following these steps:
 
-    **Windows**: Look for the service named "Microsoft Dependency agent."
+1. Is the Dependency agent installed successfully? Check to see if the service is installed and running.
 
-    **Linux**: Look for the running process "microsoft-dependency-agent."
+    - **Windows**: Look for the service named "Microsoft Dependency agent."
+    - **Linux**: Look for the running process "microsoft-dependency-agent."
 
-2. Are you on the [Free pricing tier of Log Analytics](/previous-versions/azure/azure-monitor/insights/solutions)? The Free plan allows for up to five unique computers. Any subsequent computers won't show up on the map, even if the prior five are no longer sending data.
+1. Are you on the [Free pricing tier of Log Analytics](/previous-versions/azure/azure-monitor/insights/solutions)? The Free plan allows for up to five unique computers. Any subsequent computers won't show up on the map, even if the prior five are no longer sending data.
 
-3. Is the computer sending log and perf data to Azure Monitor Logs? Perform the following query for your computer:
+1. Is the computer sending log and perf data to Azure Monitor Logs? Perform the following query for your computer:
 
     ```Kusto
     Usage | where Computer == "computer-name" | summarize sum(Quantity), any(QuantityUnit) by DataType
     ```
 
-    Did it return one or more results? Is the data recent? If so, your Log Analytics agent is operating correctly and communicating with the service. If not, check the agent on your server: [Log Analytics agent for Windows troubleshooting](../agents/agent-windows-troubleshoot.md) or [Log Analytics agent for Linux troubleshooting](../agents/agent-linux-troubleshoot.md).
+    Did it return one or more results? Is the data recent? If so, your Log Analytics agent is operating correctly and communicating with the service. If not, check the agent on your server. See [Log Analytics agent for Windows troubleshooting](../agents/agent-windows-troubleshoot.md) or [Log Analytics agent for Linux troubleshooting](../agents/agent-linux-troubleshoot.md).
 
 #### Computer appears on the map but has no processes
 
-If you see your server on the map, but it has no process or connection data, that indicates that the Dependency agent is installed and running, but the kernel driver didn't load.
-
-Check the C:\Program Files\Microsoft Dependency Agent\logs\wrapper.log file (Windows) or /var/opt/microsoft/dependency-agent/log/service.log file (Linux). The last lines of the file should indicate why the kernel didn't load. For example, the kernel might not be supported on Linux if you updated your kernel.
+You see your server on the map, but it has no process or connection data. In this case, the Dependency agent is installed and running, but the kernel driver didn't load.
 
+Check the *C:\Program Files\Microsoft Dependency Agent\logs\wrapper.log* file (Windows) or */var/opt/microsoft/dependency-agent/log/service.log* file (Linux). The last lines of the file should indicate why the kernel didn't load. For example, the kernel might not be supported on Linux if you updated your kernel.
 
 ## Next steps
 
 Now that monitoring is enabled for your virtual machines, this information is available for analysis with VM insights.
 
 - To view discovered application dependencies, see [View VM insights Map](vminsights-maps.md).
-
 - To identify bottlenecks and overall utilization with your VM's performance, see [View Azure VM performance](vminsights-performance.md).