You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/vm/vminsights-health-alerts.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,24 +80,26 @@ Notification received at time t2
80
80
- To know more about this state transition: Navigation link to the state transition happened at time t2.
81
81
82
82
## Configure notifications
83
-
To be proactively notified of an alert triggered by guest health, create an [action group](../alerts/action-groups.md) to define the different actions to perform such as sending an SMS message or starting a Logic App. Then create an [action rule](../alerts/alerts-action-rules.md) that specifies the scope of monitors and virtual machines and uses that action group.
83
+
To be proactively notified of an alert triggered by guest health, create an [action group](../alerts/action-groups.md) to define the different actions to perform such as sending an SMS message or starting a Logic App. Then create an [alert processing rule](../alerts/alerts-action-rules.md) that specifies the scope of monitors and virtual machines and uses that action group.
84
84
85
-
In the **Monitor** menu in the Azure portal, select **Alerts**. Select **Manage actions** and then **Action rules (preview)**.
85
+
In the **Monitor** menu in the Azure portal, select **Alerts** and then **Alert processing rules (preview)**.
Click **Create** to create a new alert processing rule.
88
89
89
-
Click **New action rule** to create a new rule. Click **Select** next to scope and select either a subscription, resource group, or one or more specific virtual machines. The notification will only be fired for virtual machines that fall within the scope.
On the **Scope tab**, click **Select scope** and select either a subscription, resource group, or one or more specific virtual machines. The notification will only be fired for virtual machines that fall within the scope. Add a filter where **Monitor service Equals VM Insights - Health**. Add other filters to specify the particular alerts that should trigger the notification. For example, you can use **Severity** to match alerts from all monitors that match a particular severity.
92
93
93
-
Click **Add** next to **Filter**. Create a filter where **Monitor service Equals VM Insights - Health**. Add other filters to specify the particular alerts that should trigger the notification. For example, you can use **Severity** to match alerts from all monitors that match a particular severity.
Select the **Rule settings** tab, and select **Apply action group** for the **Rule type**. Click **Add action groups** and then select the action group to associate with the monitor. Give the rule a name and select the resource group it should be saved in. Click **Create** to create the rule.
96
97
97
-
In **Define on this scope**, select **Action group** and then select the action group to associate with the monitor. Give the rule a name and select the resource group it should be saved in. Click **Create** to create the rule.
Select the **Details** tab. Select a **Subscription** and **Resource group** to store the alert processing rule and provide a descriptive **Rule name**. Click **Remove + create** to create and enable the alert processing rule.
0 commit comments