Skip to content

Commit fb03e68

Browse files
authored
Merge pull request #153680 from ofirmanor/patch-7
Update alerts-action-rules.md
2 parents 5f534eb + 9059ea6 commit fb03e68

File tree

1 file changed

+13
-6
lines changed

1 file changed

+13
-6
lines changed

articles/azure-monitor/alerts/alerts-action-rules.md

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Action rules for Azure Monitor alerts
33
description: Understanding what action rules in Azure Monitor are and how to configure and manage them.
44
ms.topic: conceptual
5-
ms.date: 03/15/2021
5+
ms.date: 04/08/2021
66

77
---
88

@@ -63,7 +63,7 @@ The available filters are:
6363

6464
* **Severity**
6565
This rule will apply only to alerts with the selected severities.
66-
For example, **severity = Sev1** means that the rule will apply only to alerts with Sev1 severity.
66+
For example, **severity = "Sev1"** means that the rule will apply only to alerts with Sev1 severity.
6767
* **Monitor service**
6868
This rule will apply only to alerts coming from the selected monitoring services.
6969
For example, **monitor service = “Azure Backup”** means that the rule will apply only to backup alerts (coming from Azure Backup).
@@ -75,15 +75,22 @@ This rule will apply only to alerts coming from a specific alert rule. The value
7575
For example, **alert rule ID = "/subscriptions/SubId1/resourceGroups/RG1/providers/microsoft.insights/metricalerts/API-Latency"** means this rule will apply only to alerts coming from "API-Latency" metric alert rule.
7676
_NOTE - you can get the proper alert rule ID by listing your alert rules from the CLI, or by opening a specific alert rule in the portal, clicking "Properties", and copying the "Resource ID" value._
7777
* **Monitor condition**
78-
This rule will apply only to alert events with the specified monitor condition - either **Fired** or **Resolved**.
78+
This rule will apply only to alert events with the specified monitor condition - either **"Fired"** or **"Resolved"**.
7979
* **Description**
8080
This rule will apply only to alerts that contains a specific string in the alert description field. That field contains the alert rule description.
81-
For example, **description contains 'prod'** means that the rule will only match alerts that contain the string "prod" in their description.
81+
For example, **description contains "prod"** means that the rule will only match alerts that contain the string "prod" in their description.
8282
* **Alert context (payload)**
8383
This rule will apply only to alerts that contain any of one or more specific values in the alert context fields.
84-
For example, **alert context (payload) contains 'Computer-01'** means that the rule will only apply to alerts whose payload contain the string "Computer-01".
84+
For example, **alert context (payload) contains "Computer-01"** means that the rule will only apply to alerts whose payload contain the string "Computer-01".
8585

86-
If you set multiple filters in a rule, all of them apply. For example, if you set **resource type' = Virtual Machines** and **severity' = Sev0**, then the rule will apply only for Sev0 alerts on virtual machines.
86+
> [!NOTE]
87+
> Each filter may include up to five values.
88+
> For example, a filter on monitor service may include up to five monitor service names.
89+
90+
91+
92+
93+
If you set multiple filters in a rule, all of them apply. For example, if you set **resource type = "Virtual Machines"** and **severity = "Sev0"**, then the rule will apply only for Sev0 alerts on virtual machines.
8794

8895
![Action rule filters](media/alerts-action-rules/action-rules-new-rule-creation-flow-filters.png)
8996

0 commit comments

Comments
 (0)