Merge pull request #173758 from rakeshrana44/master

Update Guest OS namespace to Guest (classic)

Author: PMEds28

articles/azure-monitor/essentials/media/metrics-troubleshoot/vm-metrics.png

@@ -51,7 +51,7 @@ By [locking the boundaries of chart y-axis](../essentials/metrics-charts.md#lock
 
 Collection of **Guest OS** metrics requires configuring the Azure Diagnostics Extension or enabling it using the **Diagnostic Settings** panel for your resource.
 
-**Solution:** If Azure Diagnostics Extension is enabled but you are still unable to see your metrics, follow steps outlined in [Azure Diagnostics Extension troubleshooting guide](../agents/diagnostics-extension-troubleshooting.md#metric-data-doesnt-appear-in-the-azure-portal). See also the troubleshooting steps for [Cannot pick Guest OS namespace and metrics](#cannot-pick-guest-os-namespace-and-metrics)
+**Solution:** If Azure Diagnostics Extension is enabled but you are still unable to see your metrics, follow steps outlined in [Azure Diagnostics Extension troubleshooting guide](../agents/diagnostics-extension-troubleshooting.md#metric-data-doesnt-appear-in-the-azure-portal). See also the troubleshooting steps for [Cannot pick Guest OS namespace and metrics](#cannot-pick-guest-namespace-and-metrics)
 
 ## “Error retrieving data” message on dashboard
 
@@ -77,15 +77,15 @@ In many cases, the perceived drop in the metric values is a misunderstanding of
 
 **Solution:** This behavior is by design. We believe that showing data as soon as we receive it is beneficial even when the data is *partial* or *incomplete*. Doing so allows you to make important conclusion sooner and start investigation right away. For example, for a metric that shows the number of failures, seeing a partial value X tells you that there were at least X failures on a given minute. You can start investigating the problem right away, rather than wait to see the exact count of failures that happened on this minute, which might not be as important. The chart will update once we receive the entire set of data, but at that time it may also show new incomplete data points from more recent minutes.
 
-## Cannot pick Guest OS namespace and metrics
+## Cannot pick Guest namespace and metrics
 
-Virtual machines and virtual machine scale sets have two categories of metrics: **Virtual Machine Host** metrics that are collected by the Azure hosting environment, and **Guest OS (classic)** metrics that are collected by the [monitoring agent](../agents/agents-overview.md) running on your virtual machines. You install the monitoring agent by enabling [Azure Diagnostic Extension](../agents/diagnostics-extension-overview.md).
+Virtual machines and virtual machine scale sets have two categories of metrics: **Virtual Machine Host** metrics that are collected by the Azure hosting environment, and **Guest  (classic)** metrics that are collected by the [monitoring agent](../agents/agents-overview.md) running on your virtual machines. You install the monitoring agent by enabling [Azure Diagnostic Extension](../agents/diagnostics-extension-overview.md).
 
-By default, Guest OS metrics are stored in Azure Storage account, which you pick from the **Diagnostic settings** tab of your resource. If Guest OS metrics aren't collected or metrics explorer cannot access them, you will only see the **Virtual Machine Host** metric namespace:
+By default, Guest (classic) metrics are stored in Azure Storage account, which you pick from the **Diagnostic settings** tab of your resource. If Guest metrics aren't collected or metrics explorer cannot access them, you will only see the **Virtual Machine Host** metric namespace:
 
-![metric image](./media/metrics-troubleshoot/vm.png)
+![metric image](./media/metrics-troubleshoot/vm-metrics.png)
 
-**Solution:** If you don't see **Guest OS (classic)** namespace and metrics in metrics explorer:
+**Solution:** If you don't see **Guest (classic)** namespace and metrics in metrics explorer:
 
 1. Confirm that [Azure Diagnostic Extension](../agents/diagnostics-extension-overview.md) is enabled and configured to collect metrics.
     > [!WARNING]
@@ -102,4 +102,4 @@ By default, Guest OS metrics are stored in Azure Storage account, which you pick
 * [Learn about getting started with Metric Explorer](metrics-getting-started.md)
 * [Learn about advanced features of Metric Explorer](../essentials/metrics-charts.md)
 * [See a list of available metrics for Azure services](./metrics-supported.md)
-* [See examples of configured charts](../essentials/metric-chart-samples.md)
+* [See examples of configured charts](../essentials/metric-chart-samples.md)