Skip to content

Commit 4bfacaf

Browse files
authored
Merge pull request #247953 from nolavime/nolavime-patch-1-2
Update azure-monitor-limits-alerts.md
2 parents fdf3936 + 11f7c59 commit 4bfacaf

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

includes/azure-monitor-limits-alerts.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,12 @@ ms.custom: "include file"
2121

2222
### Alerts API
2323
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.
2426
2527
| Resource | Default limit | Maximum limit |
2628
| --- | --- | --- |
2729
| [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 |
2931
| [All other alerts calls](/rest/api/monitor/alertsmanagement/alerts) | 1,000 calls per minute per subscription | Same as default |
3032

0 commit comments

Comments
 (0)