Skip to content

Commit 506823e

Browse files
authored
Merge pull request #78886 from ananthradhakrishnan/master
Rewording sentence to remove ambiguity.
2 parents d9f3187 + e4026b0 commit 506823e

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,13 +123,16 @@ Contoso wants to suppress notifications for all log alerts generated for 'Comput
123123

124124
### Scenario 3: Action group defined at a resource group
125125

126-
Contoso has defined [a metric alert at a subscription level](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-metric-overview#monitoring-at-scale-using-metric-alerts-in-azure-monitor), but wants to define the actions that trigger for alerts separately for their resource group 'ContosoRG'.
126+
Contoso has defined [a metric alert at a subscription level](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-metric-overview#monitoring-at-scale-using-metric-alerts-in-azure-monitor), but wants to define the actions that trigger specifically for alerts generated from their resource group 'ContosoRG'.
127127

128128
**Solution:** Create an action rule with
129129
* Scope = 'ContosoRG'
130130
* No filters
131131
* Action Group set to 'ContosoActionGroup'
132132

133+
> [!NOTE]
134+
> **Action groups defined within action rules and alert rules operate independently, with no de-duplication**. In the scenario described above, if there's an action group defined for the alert rule, it will trigger in conjunction with the action group defined in the action rule.
135+
133136
## Managing your action rules
134137

135138
You can view and manage your action rules from the list view as shown below.

0 commit comments

Comments
 (0)