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: includes/azure-monitor-limits-alerts.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,10 +21,12 @@ ms.custom: "include file"
21
21
22
22
### Alerts API
23
23
Azure Monitor alerts have several throttling limits to protect against users making an excessive number of calls. Such behavior can potentially overload the system back-end resources and jeopardize service responsiveness. The following limits are designed to protect customers from interruptions and ensure a consistent service level. The user throttling and limits are designed to affect only extreme usage scenarios. They shouldn't be relevant for typical usage.
24
+
>[!Note]
25
+
>There is a limit of API calls per instance. The exact limit number depands on the number of instances.
24
26
25
27
| Resource | Default limit | Maximum limit |
26
28
| --- | --- | --- |
27
29
|[Alerts - Get Summary](/rest/api/monitor/alertsmanagement/alerts/get-summary)| 50 calls per minute per subscription | Same as default |
28
-
|[Alerts - Get All](/rest/api/monitor/alertsmanagement/alerts/get-all) (not "Get By Id") | 100 calls per minute per subscription | Same as default |
30
+
|[Alerts - Get All](/rest/api/monitor/alertsmanagement/alerts/get-all) (not "Get By ID") | 100 calls per minute per subscription | Same as default |
29
31
|[All other alerts calls](/rest/api/monitor/alertsmanagement/alerts)| 1,000 calls per minute per subscription | Same as default |
0 commit comments