Merge pull request #258524 from hilaryw29/patch-17

Create alert-rules-automatic-repairs-service-state.md

Author: JamesJBarnett

articles/virtual-machine-scale-sets/TOC.yml

@@ -198,6 +198,8 @@
     maintainContext: true
   - name: Terminate notifications
     href: virtual-machine-scale-sets-terminate-notification.md
+  - name: Monitor automatic repairs service state
+    href: alert-rules-automatic-repairs-service-state.md
   - name: Instance Metadata service
     items:
     - name: CLI

articles/virtual-machine-scale-sets/alert-rules-automatic-repairs-service-state.md

@@ -0,0 +1,38 @@
+---
+title: Use Azure Alert Rules to monitor changes in Automatic Instance Repairs ServiceState
+description: Learn how to use Azure Alert Rules to get notified of changes to Automatic Instance Repairs ServiceState.
+author: hilaryw29
+ms.author: hilarywang
+ms.topic: how-to
+ms.service: virtual-machine-scale-sets
+ms.date: 11/14/2023
+---
+
+# Use Azure Alert Rules to monitor changes in Automatic Instance Repairs ServiceState
+
+This article shows you how to use [Alert Rules from Azure Monitor](../azure-monitor/alerts/alerts-overview.md) to receive custom notifications every time the ServiceState for Automatic Repairs is updated on your scale set. This will help track if Automatic Repairs become _Suspended_ due to VM instances remaining unhealthy after multiple repair operations. To learn more about Azure Monitor alerts, see the [alerts overview](../azure-monitor/alerts/alerts-overview.md). 
+
+To follow this tutorial, ensure that you have a Virtual Machine scale set with [Automatic Repairs](./virtual-machine-scale-sets-automatic-instance-repairs.md) enabled.
+
+## Azure portal
+1.	In the [portal](https://portal.azure.com/), navigate to your VM scale set resource
+2.	Select **Alerts** from the left pane, and then select **+ Create > Alert rule**. :::image type="content" source="media/alert-rules-automatic-repairs-service-state/picture-1.png" alt-text="Create monitoring alert in the Azure portal":::
+3.	Under the **Condition** tab, select **See all signals** and choose the signal name called “Sets the state of an orchestration service in a Virtual Machine Scale set”. Select **Apply**. :::image type="content" source="media/alert-rules-automatic-repairs-service-state/picture-2.png" alt-text="Select alert signal to monitor scale set orchestration service state":::
+4.	Set **Event Level** to “Informational” and **Status** to “Succeeded”. :::image type="content" source="media/alert-rules-automatic-repairs-service-state/picture-3.png" alt-text="Configure event level and status for alert rule":::
+5.	Under the **Actions** tab, select an existing action group or see [Create action group](#creating-an-action-group) 
+6.	Under the **Details** tab > **Alert rule name**, set a name for your alert. Then select **Review + create** > **Create** to create your alert.
+:::image type="content" source="media/alert-rules-automatic-repairs-service-state/picture-4.png" alt-text="Review and create alert rule":::
+
+Once the alert is created and enabled on your scale set, you'll receive a notification every time a change to the ServiceState is detected on your scale set.
+
+### Sample email notification from alert rule
+Below is an example of an email notification created from a configured alert rule. 
+:::image type="content" source="media/alert-rules-automatic-repairs-service-state/picture-5.png" alt-text="Sample email notification from alert rule":::
+
+## Creating an action group
+1. Under the **Actions** tab, select **Create action group**.
+:::image type="content" source="media/alert-rules-automatic-repairs-service-state/picture-6.png" alt-text="Create action group on portal":::
+2. In the **Basics** tab, provide an **Action group name** and **Display name**.
+3. Under the **Notifications** tab **> Notification type**, select “Email/SMS message/Push/Voice”. Select the **edit** button to configure how you’d like to be notified.
+:::image type="content" source="media/alert-rules-automatic-repairs-service-state/picture-7.png" alt-text="Configure notification type for action group":::
+4. Select **Review + Create > Create**

articles/virtual-machine-scale-sets/media/alert-rules-automatic-repairs-service-state/picture-1.png

@@ -54,6 +54,14 @@ Automatic repairs currently do not support scenarios where a VM instance is mark
 
 Automatic instance repair feature relies on health monitoring of individual instances in a scale set. VM instances in a scale set can be configured to emit application health status using either the [Application Health extension](./virtual-machine-scale-sets-health-extension.md) or [Load balancer health probes](../load-balancer/load-balancer-custom-probe-overview.md). If an instance is found to be unhealthy, the scale set will perform a preconfigured repair action on the unhealthy instance. Automatic instance repairs can be enabled in the Virtual Machine Scale Set model by using the `automaticRepairsPolicy` object. 
 
+The automatic instance repairs process goes as follows:
+
+1. [Application Health extension](./virtual-machine-scale-sets-health-extension.md) or [Load balancer health probes](../load-balancer/load-balancer-custom-probe-overview.md) ping the application endpoint inside each virtual machine in the scale set to get application health status for each instance.
+2. If the endpoint responds with a status 200 (OK), then the instance is marked as "Healthy". In all the other cases (including if the endpoint is unreachable), the instance is marked "Unhealthy".
+3. When an instance is found to be unhealthy, the scale set applies the configured repair action (default is *Replace*) to the unhealthy instance.
+4. Instance repairs are performed in batches. At any given time, no more than 5% of the total instances in the scale set are repaired. If a scale set has fewer than 20 instances, the repairs are done for one unhealthy instance at a time.
+5. The above process continues until all unhealthy instance in the scale set are repaired.
+
 ### Available repair actions
 
 > [!CAUTION]
@@ -92,13 +100,7 @@ Virtual Machine Scale Sets provide the capability to temporarily suspend automat
 
 If newly created instances for replacing the unhealthy ones in a scale set continue to remain unhealthy even after repeatedly performing repair operations, then as a safety measure the platform updates the *serviceState* for automatic repairs to *Suspended*. You can resume the automatic repairs again by setting the value of *serviceState* for automatic repairs to *Running*. Detailed instructions are provided in the section on [viewing and updating the service state of automatic repairs policy](#viewing-and-updating-the-service-state-of-automatic-instance-repairs-policy) for your scale set.
 
-The automatic instance repairs process works as follows:
-
-1. [Application Health extension](./virtual-machine-scale-sets-health-extension.md) or [Load balancer health probes](../load-balancer/load-balancer-custom-probe-overview.md) ping the application endpoint inside each virtual machine in the scale set to get application health status for each instance.
-2. If the endpoint responds with a status 200 (OK), then the instance is marked as "Healthy". In all the other cases (including if the endpoint is unreachable), the instance is marked "Unhealthy".
-3. When an instance is found to be unhealthy, the scale set applies the configured repair action (default is *Replace*) to the unhealthy instance.
-4. Instance repairs are performed in batches. At any given time, no more than 5% of the total instances in the scale set are repaired. If a scale set has fewer than 20 instances, the repairs are done for one unhealthy instance at a time.
-5. The above process continues until all unhealthy instance in the scale set are repaired.
+You can also set up Azure Alert Rules to monitor *serviceState* changes and get notified if automatic repairs becomes suspended on your scale set. For details, see [Use Azure alert rules to monitor changes in automatic instance repairs service state](./alert-rules-automatic-repairs-service-state.md).
 
 ## Instance protection and automatic repairs