Skip to content

Commit 856f247

Browse files
authored
Link to Log Analytics throttling guidance from Monitor Query README (Azure#20759)
1 parent ee9d553 commit 856f247

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

sdk/monitor/azure-monitor-query/README.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -69,13 +69,7 @@ For examples of Logs and Metrics queries, see the [Examples](#examples) section.
6969

7070
### Logs query rate limits and throttling
7171

72-
Each Azure Active Directory user is able to make up to 200 requests per 30 seconds, with no cap on the total calls per day. If requests are made at a rate higher than this, these requests will receive HTTP status code 429 (Too Many Requests) along with the `Retry-After: <delta-seconds>` header. The header indicates the number of seconds until requests to this app are likely to be accepted.
73-
74-
In addition to call rate limits and daily quota caps, there are limits on queries themselves. Queries cannot:
75-
76-
- Return more than 500,000 rows.
77-
- Return more than 64,000,000 bytes (~61 MiB total data).
78-
- Run longer than 10 minutes by default. See this for details.
72+
The Log Analytics service applies throttling when the request rate is too high. Limits, such as the maximum number of rows returned, are also applied on the Kusto queries. For more information, see [Rate and query limits](https://dev.loganalytics.io/documentation/Using-the-API/Limits).
7973

8074
### Metrics data structure
8175

0 commit comments

Comments
 (0)