Skip to content

Commit 0838a27

Browse files
Merge pull request #185179 from ishasahni1/patch-20
Added Test action rate limits
2 parents 4858ac7 + 2aec0ff commit 0838a27

File tree

8 files changed

+788
-7
lines changed

8 files changed

+788
-7
lines changed

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

Lines changed: 32 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,9 @@ title: Create and manage action groups in the Azure portal
33
description: Learn how to create and manage action groups in the Azure portal.
44
author: dkamstra
55
ms.topic: conceptual
6-
ms.date: 11/18/2021
6+
ms.date: 01/15/2022
77
ms.author: dukek
8+
ms.custom: references_regions
89
---
910
# Create and manage action groups in the Azure portal
1011
An action group is a collection of notification preferences defined by the owner of an Azure subscription. Azure Monitor, Service Health and Azure Advisor alerts use action groups to notify users that an alert has been triggered. Various alerts may use the same action group or different action groups depending on the user's requirements.
@@ -94,6 +95,33 @@ Under **Instance details**:
9495

9596
> [!NOTE]
9697
> When you configure an action to notify a person by email or SMS, they receive a confirmation indicating they have been added to the action group.
98+
### Test an action group in the Azure portal (Preview)
99+
100+
When creating or updating an action group in the Azure portal, you can **test** the action group.
101+
1. After creating an action rule, click on **Review + create**. Select *Test action group*.
102+
103+
![The Test Action Group](./media/action-groups/test-action-group.png)
104+
105+
1. Select the *sample type* and select the notification and action types that you want to test and select **Test**.
106+
107+
![Select Sample Type + notification + action type](./media/action-groups/test-sample-action-group.png)
108+
109+
1. If you close the window or select **Back to test setup** while the test is running, the test is stopped, and you will not get test results.
110+
111+
![Stop running test](./media/action-groups/stop-running-test.png)
112+
113+
1. When the test is complete either a **Success** or **Failed** test status is displayed. If the test failed, you could select *View details* to get more information.
114+
![Test sample failed](./media/action-groups/test-sample-failed.png)
115+
116+
You can use the information in the **Error details section**, to understand the issue so that you can edit and test the action group again.
117+
To allow you to check the action groups are working as expected before you enable them in a production environment, you will get email and SMS alerts with the subject: Test.
118+
119+
All the details and links in Test email notifications for the alerts fired are a sample set for reference.
120+
121+
> [!NOTE]
122+
> You may have a limited number of actions in a test Action Group. See the [rate limiting information](./alerts-rate-limiting.md) article.
123+
>
124+
> You can opt in or opt out to the common alert schema through Action Groups, on the portal. You can [find common schema samples for test action groups for all the sample types](./alerts-common-schema-test-action-definitions.md).
97125
98126
## Manage your action groups
99127

@@ -153,11 +181,11 @@ While setting up *Email ARM Role* you need to make sure below 3 conditions are m
153181
> [!NOTE]
154182
> It can take upto **24 hours** for customer to start receiving notifications after they add new ARM Role to their subscription.
155183
156-
### Event Hub (Preview)
184+
### Event hub (preview)
157185
> [!NOTE]
158-
> The Event Hub action type is currently in *Preview*. During the preview there may be bugs and disruptions in availability of the functionality.
186+
> The event hub action type is currently in *Preview*. During the preview there may be bugs and disruptions in availability of the functionality.
159187
160-
An Event Hub action publishes notifications to an [Azure Event Hub](~/articles/event-hubs/event-hubs-about.md). You may then subscribe to the alert notification stream from your event receiver.
188+
An event hub action publishes notifications to [Azure Event Hubs](~/articles/event-hubs/event-hubs-about.md). You may then subscribe to the alert notification stream from your event receiver.
161189

162190
### Function
163191
Calls an existing HTTP trigger endpoint in [Azure Functions](../../azure-functions/functions-get-started.md). To handle a request, your endpoint must handle the HTTP POST verb.

articles/azure-monitor/alerts/alerts-common-schema-test-action-definitions.md

Lines changed: 743 additions & 0 deletions
Large diffs are not rendered by default.

articles/azure-monitor/alerts/alerts-rate-limiting.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,22 @@ ms.date: 3/12/2018
1010
# Rate limiting for Voice, SMS, emails, Azure App push notifications and webhook posts
1111
Rate limiting is a suspension of notifications that occurs when too many are sent to a particular phone number, email address or device. Rate limiting ensures that alerts are manageable and actionable.
1212

13-
The rate limit thresholds are:
13+
The rate limit thresholds in **production** are:
1414

1515
- **SMS**: No more than 1 SMS every 5 minutes.
1616
- **Voice**: No more than 1 Voice call every 5 minutes.
1717
- **Email**: No more than 100 emails in an hour.
1818

1919
Other actions are not rate limited.
2020

21+
The rate limit thresholds for **test action group** are:
22+
23+
- **SMS**: No more than 1 SMS every 1 minute.
24+
- **Voice**: No more than 1 Voice call every 1 minute.
25+
- **Email**: No more than 2 emails in every 1 minute.
26+
27+
Other actions are not rate limited.
28+
2129
## Rate limit rules
2230
- A particular phone number or email is rate limited when it receives more messages than the threshold allows.
2331
- A phone number or email can be part of action groups across many subscriptions. Rate limiting applies across all subscriptions. It applies as soon as the threshold is reached, even if messages are sent from multiple subscriptions.
@@ -26,4 +34,4 @@ The rate limit thresholds are:
2634
## Next steps ##
2735
* Learn more about [SMS alert behavior](alerts-sms-behavior.md).
2836
* Get an [overview of activity log alerts](./alerts-overview.md), and learn how to receive alerts.
29-
* Learn how to [configure alerts whenever a service health notification is posted](../../service-health/alerts-activity-log-service-notifications-portal.md).
37+
* Learn how to [configure alerts whenever a service health notification is posted](../../service-health/alerts-activity-log-service-notifications-portal.md).
36.2 KB
Loading
87.5 KB
Loading
39 KB
Loading
32.9 KB
Loading

articles/azure-monitor/toc.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -586,6 +586,8 @@ items:
586586
href: alerts/alerts-common-schema.md
587587
- name: Common alert schema definition
588588
href: alerts/alerts-common-schema-definitions.md
589+
- name: Common alert schema definition for Test action group
590+
href: alerts/alerts-common-schema-test-action-definitions.md
589591
- name: Integrate the common alert schema with Logic Apps
590592
href: alerts/alerts-common-schema-integrations.md
591593
- name: SMS alert behavior
@@ -1556,4 +1558,4 @@ items:
15561558
- name: Pricing calculator
15571559
href: https://azure.microsoft.com/pricing/calculator/
15581560
- name: Regional availability
1559-
href: https://azure.microsoft.com/global-infrastructure/services/?regions=all&products=monitor
1561+
href: https://azure.microsoft.com/global-infrastructure/services/?regions=all&products=monitor

0 commit comments

Comments
 (0)