Merge pull request #190206 from bwren/vm-health-migrate

tamarakhader · web-flow · commit 91a4edfade8e · 2022-05-04T23:55:29.000-04:00
VM insights guest health migration
diff --git a/articles/azure-monitor/azure-monitor-operations-manager.md b/articles/azure-monitor/azure-monitor-operations-manager.md
@@ -91,11 +91,6 @@ When you move machines to the cloud, the monitoring requirements for their softw
 
 Azure Monitor also doesn't measure the health of different applications and services running on a virtual machine. Metric alerts can automatically resolve when a value drops below a threshold, but Azure Monitor doesn't currently have the ability to define health criteria for applications and services running on the machine, nor does it provide health rollup to group the health of related components.
 
-> [!NOTE]
-> A new [guest health feature for VM insights](vm/vminsights-health-overview.md) is now in public preview and does alert based on the health state of a set of performance metrics. This is initially limited though to a specific set of performance counters related to the guest operating system and not applications or other workloads running in the virtual machine.
-> 
-> [![VM insights guest health](media/azure-monitor-operations-manager/vm-insights-guest-health.png)](media/azure-monitor-operations-manager/vm-insights-guest-health.png#lightbox)
-
 Monitoring the software on your machines in a hybrid environment will typically use a combination of VM insights and Operations Manager, depending on the requirements of each machine and on your maturity developing operational processes around Azure Monitor. The Microsoft Management Agent (referred to as the Log Analytics agent in Azure Monitor) is used by both platforms so that a single machine can be simultaneously monitored by both.
 
 > [!NOTE]
diff --git a/articles/azure-monitor/toc.yml b/articles/azure-monitor/toc.yml
@@ -1205,6 +1205,8 @@ items:
       items:
       - name: Overview
         href: vm/vminsights-health-overview.md
+      - name: Migrate
+        href: vm/vminsights-health-migrate.md
       - name: Enable
         href: vm/vminsights-health-enable.md
       - name: Alerts
diff --git a/articles/azure-monitor/vm/media/monitor-virtual-machines/vminsights-get-started.png b/articles/azure-monitor/vm/media/monitor-virtual-machines/vminsights-get-started.png
diff --git a/articles/azure-monitor/vm/vminsights-health-alerts.md b/articles/azure-monitor/vm/vminsights-health-alerts.md
@@ -4,13 +4,15 @@ description: Describes the alerts created by VM insights guest health including
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
-ms.date: 11/10/2020
+ms.date: 05/03/2022
 
 ---
 
 # VM insights guest health alerts (preview)
 VM insights guest health allows you to view the health of a virtual machine as defined by a set of performance measurements that are sampled at regular intervals. An alert can be created when a virtual machine or monitor changes to an unhealthy state. You can view and manage these alerts with [those created by alert rules in Azure Monitor](../alerts/alerts-overview.md) and choose to be proactively notified when a new alert is created.
 
+[!INCLUDE [guest-health-deprecate](../../../includes/azure-monitor-guest-health-deprecation.md)]
+
 ## Configure alerts
 You cannot create an explicit alert rule for VM insights guest health while this feature is in preview. By default, alerts will be created for each virtual machine but not for each monitor.  This means that if a monitor changes to a state that doesn't affect the current state of the virtual machine, then no alert is created because the virtual machine state didn't change. 
 
diff --git a/articles/azure-monitor/vm/vminsights-health-configure-dcr.md b/articles/azure-monitor/vm/vminsights-health-configure-dcr.md
@@ -4,13 +4,15 @@ description: Describes how to modify default monitoring in VM insights guest hea
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
-ms.date: 10/15/2020
+ms.date: 05/03/2022
 
 ---
 
 # Configure monitoring in VM insights guest health using data collection rules (preview)
 [VM insights guest health](vminsights-health-overview.md) allows you to view the health of a virtual machine as defined by a set of performance measurements that are sampled at regular intervals. This article describes how you can modify default monitoring across multiple virtual machines using data collection rules.
 
+[!INCLUDE [guest-health-deprecate](../../../includes/azure-monitor-guest-health-deprecation.md)]
+
 
 ## Monitors
 The health state of a virtual machine is determined by the [rollup of health](vminsights-health-overview.md#health-rollup-policy) from each of its monitors. There are two types of monitors in VM insights guest health as shown in the following table.
diff --git a/articles/azure-monitor/vm/vminsights-health-configure.md b/articles/azure-monitor/vm/vminsights-health-configure.md
@@ -4,13 +4,16 @@ description: Describes how to modify default monitoring for VM insights guest he
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
-ms.date: 12/14/2020
+ms.date: 05/03/2022
 
 ---
 
 # Configure monitoring in VM insights guest health (preview)
 VM insights guest health allows you to view the health of a virtual machine as defined by a set of performance measurements that are sampled at regular intervals. This article describes how you can modify default monitoring using the Azure portal. It also describes fundamental concepts of monitors required for [configuring monitoring using a data collection rule](vminsights-health-configure-dcr.md).
 
+[!INCLUDE [guest-health-deprecate](../../../includes/azure-monitor-guest-health-deprecation.md)]
+
+
 ## Open monitor configuration
 Open monitor configuration in the Azure portal by selecting the monitor and then the **Configuration** tab.
 
diff --git a/articles/azure-monitor/vm/vminsights-health-enable.md b/articles/azure-monitor/vm/vminsights-health-enable.md
@@ -4,14 +4,17 @@ description: Describes how to enable VM insights guest health in your subscripti
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
-ms.date: 04/05/2021
+ms.date: 05/03/2022
 ms.custom: references_regions, devx-track-azurepowershell
 
 ---
 
 # Enable VM insights guest health (preview)
 VM insights guest health allows you to view the health of a virtual machine as defined by a set of performance measurements that are sampled at regular intervals. This article describes how to enable this feature in your subscription and how to enable guest monitoring for each virtual machine.
 
+[!INCLUDE [guest-health-deprecate](../../../includes/azure-monitor-guest-health-deprecation.md)]
+
+
 ## Current limitations
 VM insights guest health has the following limitations in public preview:
 
diff --git a/articles/azure-monitor/vm/vminsights-health-migrate.md b/articles/azure-monitor/vm/vminsights-health-migrate.md
@@ -0,0 +1,91 @@
+---
+title: Migrate from VM insights guest health (preview) to Azure Monitor log alerts
+description: Describes how to migrate from VM insights guest health to Azure Monitor log alerts.
+ms.topic: conceptual
+ms.date: 03/01/2022
+
+---
+
+# Migrate from VM insights guest health to Azure Monitor log alerts
+This article walks through migrating from the VM insights guest health (preview) to Azure Monitor log alerts to configure alerts on key VM metrics and offboard VMs from VM insights guest health (preview). [VM insights guest health (preview)](vminsights-health-overview.md) will retire on 30 November 2022. If you are using this feature to configure alerts on VM metrics (CPU utilization, Available memory, Free disk space), make sure to transition to Azure Monitor log alerts before this date. 
+
+## Configure Azure Monitor log alerts
+Before you remove VM insights guest health, you should create alert rules to replace its alerting functionality. See [Monitor virtual machines with Azure Monitor: Alerts](monitor-virtual-machine-alerts.md#log-alerts) for instructions on creating Azure Monitor log alerts. 
+
+> [!IMPORTANT]
+> Transitioning to log alerts will result in charges according to Azure Monitor log alert rates. See [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/) for details.
+
+
+Alert rules for the key metrics used by VM health include the following:
+
+- [CPU utilization](monitor-virtual-machine-alerts.md#log-alert-rules)
+- [Available memory](monitor-virtual-machine-alerts.md#log-alert-rules-1)
+- [Free disk space](monitor-virtual-machine-alerts.md#log-query-alert-rules-1)
+
+To create a an alert rule for a single VM that alerts on any of the three conditions, create a [log alert rule](monitor-virtual-machine-alerts.md#log-alerts) with the following details.
+
+
+| Setting | Value |
+|:---|:---|
+| **Scope** | |
+| Target scope | Select your virtual machine. |
+| **Condition** | |
+| Signal type | Log |
+| Signal name | Custom log search |
+| Query | \<Use the query below\> |
+| Measurement | Measure: *Table rows*<br>Aggregation type: Count<br>Aggregation granularity: 15 minutes |
+| Alert Logic | Operator: Greater than<br>Threshold value: 0<br>Frequency of evaluation: 15 minutes |
+| Actions | Select or add an [action group](../alerts/action-groups.md) to notify you when the threshold is exceeded. |
+| **Details** | |
+| Severity| Warning |
+| Alert rule name | Daily data limit reached |
+
+Replace the values in the following query if you want to set different thresholds.
+
+```kusto
+InsightsMetrics
+| where TimeGenerated >= ago(15m)
+| where Origin == "vm.azm.ms"
+| where Namespace == "Processor" and Name == "UtilizationPercentage"
+| summarize UtilizationPercentage = avg(Val) by Computer, _ResourceId
+| where UtilizationPercentage >= 90
+| union (
+InsightsMetrics
+| where TimeGenerated >= ago(15m)
+| where Origin == "vm.azm.ms"
+| where Namespace == "Memory" and Name == "AvailableMB"
+| summarize AvailableMB = avg(Val) by Computer, _ResourceId
+| where AvailableMB <= 100)
+| union (
+InsightsMetrics
+| where Origin == "vm.azm.ms"
+| where TimeGenerated >= ago(15m)
+| where Namespace == "LogicalDisk" and Name == "FreeSpacePercentage"
+| summarize FreeSpacePercentage = avg(Val) by Computer, _ResourceId
+| where FreeSpacePercentage <= 10)
+| summarize UtilizationPercentage = max(UtilizationPercentage), AvailableMB = max(AvailableMB), FreeSpacePercentage = max(FreeSpacePercentage)  by Computer, _ResourceId
+```
+
+## Offboard VMs from VM insights guest health
+Use the following steps to offboard the VMs from the VM insights guest health (preview) feature. The **Health** tab and the **Guest VM Health** status in VM insights will not be available after retirement.
+
+
+### 1. Uninstall the VM extension for VM insights guest health
+The VM Extension is called *GuestHealthWindowsAgent* for Windows VMs and *GuestHealthLinuxAgent* for Linux VMs. You can remove the extension from the **Extensions + applications** page for the virtual machine in the Azure portal, [Azure PowerShell](/powershell/module/az.compute/remove-azvmextension), or [Azure CLI](/cli/azure/vm/extension#az-vm-extension-delete).
+
+
+### 2. Delete the Data Collection Rule Association created for VM insights guest health
+Before you can remove the data collection rule for VM insights guest health, you need to remove its association with any VMs. If the VM was onboarded to VM insights guest health using the Azure portal, a default DCR with a name similar to *Microsoft-VMInsights-Health-xxxxx* will have been created. If you onboarded with another method, you may have given the DCR a different name.
+
+From the **Monitor** menu in the Azure portal, select **Data Collection Rules**. Click on the DCR for VM insights guest health, and then select **Resources**. Select the VMs to remove and click **Delete**.
+
+You can also remove the Data Collection Rule Association using [Azure PowerShell](../agents/data-collection-rule-azure-monitor-agent.md#manage-rules-and-association-using-powershell) or [Azure CLI](/cli/azure/monitor/data-collection/rule/association#az-monitor-data-collection-rule-association-delete). 
+
+
+### 3. Delete Data Collection Rule created for VM insights guest health
+To remove the data collection rule, click **Delete** from the DCR page in the Azure portal. You can also delete the Data Collection Rule using [Azure PowerShell](../agents/data-collection-rule-azure-monitor-agent.md#manage-rules-and-association-using-powershell) or [Azure CLI](/cli/azure/monitor/data-collection/rule#az-monitor-data-collection-rule-delete).
+
+
+## Next steps
+
+- [Read more about log query alerts for virtual machine](monitor-virtual-machine-alerts.md)
diff --git a/articles/azure-monitor/vm/vminsights-health-overview.md b/articles/azure-monitor/vm/vminsights-health-overview.md
@@ -4,13 +4,16 @@ description: Overview of the health feature in VM insights including how you can
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
-ms.date: 10/27/2020
+ms.date: 05/03/2022
 
 ---
 
 # VM insights guest health (preview)
 VM insights guest health allows you to view the health of virtual machines based on a set of performance measurements that are sampled at regular intervals from the guest operating system. You can quickly check the health of all virtual machines in a subscription or resource group, drill down on the detailed health of a particular virtual machine, or be proactively notified when a virtual machine becomes unhealthy. 
 
+[!INCLUDE [guest-health-deprecate](../../../includes/azure-monitor-guest-health-deprecation.md)]
+
+
 ## Enable virtual machine health
 See [Enable VM insights guest health (preview)](vminsights-health-enable.md) for details on enabling the guest health feature and onboarding virtual machines.
 
diff --git a/articles/azure-monitor/vm/vminsights-health-troubleshoot.md b/articles/azure-monitor/vm/vminsights-health-troubleshoot.md
@@ -4,15 +4,17 @@ description: Describes troubleshooting steps that you can take when you have iss
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
-ms.date: 02/25/2021
+ms.date: 05/03/2022
 
 ---
 
 # Troubleshoot VM insights guest health (preview)
 This article describes troubleshooting steps that you can take when you have issues with VM insights health.
 
+[!INCLUDE [guest-health-deprecate](../../../includes/azure-monitor-guest-health-deprecation.md)]
+
 ## Installation errors
-If any of the following solutions do not solve your installation issue, collect VM Health agent log located at `/var/log/azure/Microsoft.Azure.Monitor.VirtualMachines.GuestHealthLinuxAgent/*.log` and contact Microsoft for further investigation.
+If any of the following solutions don't solve your installation issue, collect VM Health agent log located at `/var/log/azure/Microsoft.Azure.Monitor.VirtualMachines.GuestHealthLinuxAgent/*.log` and contact Microsoft for further investigation.
 
 ### Error message showing db5 error
 Your installation didn't succeed and your installation error message is similar to the following:
@@ -33,7 +35,7 @@ Your installation didn't succeed and your installation error message is similar
 Exiting with the following error: "Failed to install VM Guest Health Agent: Init already exists: /etc/systemd/system/vmGuestHealthAgent.service"install vmGuestHealthAgent service execution failed with exit code 37
 ```
 
-VM Health Agent will uninstall the existing service first before installing the current version. The reason for this error is likely because the previous service file didn't get cleaned up due to some reason. Login to the VM and run the following command backup existing service file and try re-install again.
+VM Health Agent will uninstall the existing service first before installing the current version. The reason for this error is likely because the previous service file didn't get cleaned up due to some reason. Log in to the VM and run the following command backup existing service file and try re-install again.
 
 ```
 sudo mv /etc/systemd/system/vmGuestHealthAgent.service  /etc/systemd/system/vmGuestHealthAgent.service.bak
@@ -51,28 +53,28 @@ Your installation didn't succeed and your installation error message is similar
 ```
 Exiting with the following error: "Failed to install VM Guest Health Agent: exit status 1"install vmGuestHealthAgent service execution failed with exit code 37
 ```
-This is likely because VM Guest Agent couldn't acquire the lock for the service file. Try to reboot your VM which will release the lock.
+This is likely because VM Guest Agent couldn't acquire the lock for the service file. Try to reboot your VM, which will release the lock.
 
 
 ## Upgrade errors
 
 ### Upgrade available message is still displayed after upgrading guest health 
 
-- Verify that VM is running in global Azure. Azure Arc-enabled servers are not yet supported.
+- Verify that VM is running in global Azure. Azure Arc-enabled servers aren't yet supported.
 - Verify that the virtual machine's region and operating system version are supported as described in [Enable Azure Monitor for VMs guest health (preview)](vminsights-health-enable.md).
 - Verify that guest health extension installed successfully with 0 exit code.
 - Verify that Azure Monitor agent extension is installed successfully.
 - Verify that system-assigned managed identity is enabled for the virtual machine.
 - Verify that no user-assigned managed identities are specified for the virtual machine.
-- Verify for Windows virtual machines that locale is *US English*. Localization is not currently supported by Azure Monitor agent.
-- Verify that the virtual machine is not using the network proxy. Azure Monitor agent does not currently support proxies.
+- Verify for Windows virtual machines that locale is *US English*. Localization isn't currently supported by Azure Monitor agent.
+- Verify that the virtual machine isn't using the network proxy. Azure Monitor agent doesn't currently support proxies.
 - Verify that the health extension agent started without errors. If the agent can't start, the agent's state may be corrupt. Delete the contents of the agent state folder and restart the agent.
   - For Linux: Daemon is *vmGuestHealthAgent*. State folder is */var/opt/vmGuestHealthAgent/**
   - For Windows: Service is *VM Guest Health agent*. State folder is _%ProgramData%\Microsoft\VMGuestHealthAgent\\*_.
 - Verify the Azure Monitor agent has network connectivity. 
   - From the virtual machine, attempt to ping _\<region\>.handler.control.monitor.azure.com_. For example, for a virtual machine in westeurope, attempt to ping _westeurope.handler.control.monitor.azure.com:443_.
 - Verify that virtual machine has an association with a data collection rule in the same region as the Log Analytics workspace.
-  -  Refer to **Create data collection rule (DCR)** in [Enable Azure Monitor for VMs guest health (preview)](vminsights-health-enable.md) to ensure structure of the DCR is correct. Pay particular attention to presence of *performanceCounters* data source section set up to samples three counters and presence of *inputDataSources* section in health extension configuration to send counters to the extension.
+  -  Refer to **Create data collection rule (DCR)** in [Enable Azure Monitor for VMs guest health (preview)](vminsights-health-enable.md) to ensure structure of the DCR is correct. Pay particular attention to presence of *performanceCounters* data source section setup to samples three counters and presence of *inputDataSources* section in health extension configuration to send counters to the extension.
 -  Check the virtual machine for guest health extension errors.
    -  For Linux: Check logs at _/var/log/azure/Microsoft.Azure.Monitor.VirtualMachines.GuestHealthLinuxAgent/*.log_.
    -  For Windows: Check logs at _C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.Monitor.VirtualMachines.GuestHealthWindowsAgent\{extension version}\*.log_.
@@ -90,7 +92,7 @@ This is likely because VM Guest Agent couldn't acquire the lock for the service
 
 #### Verify that the virtual machine meets configuration requirements
 
-1. Verify that the virtual machine is an Azure virtual machine. Azure Arc for servers is not currently supported.
+1. Verify that the virtual machine is an Azure virtual machine. Azure Arc for servers isn't currently supported.
 2. Verify that the virtual machine is running a [supported operating system](vminsights-health-enable.md?current-limitations.md).
 3. Verify that the virtual machine is installed in a [supported region](vminsights-health-enable.md?current-limitations.md).
 4. Verify that the Log Analytics workspace is installed in a [supported region](vminsights-health-enable.md?current-limitations.md).
@@ -116,7 +118,7 @@ This error indicates that the **Microsoft.WorkloadMonitor** resource provider wa
 ### Health shows as "unknown" after guest health is enabled.
 
 #### Verify that performance counters on Windows nodes are working correctly 
-Guest health relies on the agent being able to collect performance counters from the node. he base set of performance counter libraries may become corrupted and may need to be rebuilt. Follow the instructions at [Manually rebuild performance counter library values](/troubleshoot/windows-server/performance/rebuild-performance-counter-library-values) to rebuild the performance counters.
+Guest health relies on the agent being able to collect performance counters from the node. the base set of performance counter libraries may become corrupted and may need to be rebuilt. Follow the instructions at [Manually rebuild performance counter library values](/troubleshoot/windows-server/performance/rebuild-performance-counter-library-values) to rebuild the performance counters.
 
 
 
diff --git a/includes/azure-monitor-guest-health-deprecation.md b/includes/azure-monitor-guest-health-deprecation.md
