Skip to content

Commit 9dc6849

Browse files
committed
edit pass: two-alerts-articles
1 parent a2e386d commit 9dc6849

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

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

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -19,11 +19,9 @@ Alert processing rules allow you to apply processing on fired alerts. You might
1919

2020
You can use alert processing rules to add [action groups](./action-groups.md) or remove (suppress) action groups from your fired alerts. You can apply alert processing rules to different resource scopes, from a single resource, or to an entire subscription. You can also use them to apply various filters or have the rule work on a predefined schedule.
2121

22-
## What are alert processing rules useful for?
23-
2422
Some common use cases for alert processing rules are described here.
2523

26-
### Notification suppression during planned maintenance
24+
## Suppress notifications during planned maintenance
2725

2826
Many customers set up a planned maintenance time for their resources, either on a one-time basis or on a regular schedule. The planned maintenance might cover a single resource, like a virtual machine, or multiple resources, like all virtual machines in a resource group. So, you might want to stop receiving alert notifications for those resources during the maintenance window. In other cases, you might prefer to not receive alert notifications outside of your business hours. Alert processing rules allow you to achieve that.
2927

@@ -35,13 +33,13 @@ You could alternatively suppress alert notifications by disabling the alert rule
3533

3634
In all these cases, an alert processing rule provides an easy way to achieve the notification suppression goal.
3735

38-
### Management at scale
36+
## Management at scale
3937

4038
Most customers tend to define a few action groups that are used repeatedly in their alert rules. For example, they might want to call a specific action group whenever any high-severity alert is fired. As their number of alert rules grows, manually making sure that each alert rule has the right set of action groups is becoming harder.
4139

4240
Alert processing rules allow you to specify that logic in a single rule, instead of having to set it consistently in all your alert rules. They also cover alert types that aren't generated by an alert rule.
4341

44-
### Add action groups to all alert types
42+
## Add action groups to all alert types
4543

4644
Azure Monitor alert rules let you select which action groups will be triggered when their alerts are fired. However, not all Azure alert sources let you specify action groups. Some examples of such alerts include [Azure Backup alerts](../../backup/backup-azure-monitoring-built-in-monitor.md), [VM Insights guest health alerts](../vm/vminsights-health-alerts.md), [Azure Stack Edge](../../databox-online/azure-stack-edge-gpu-manage-device-event-alert-notifications.md), and Azure Stack Hub.
4745

0 commit comments

Comments
 (0)