Skip to content

Commit dfe3b47

Browse files
Merge pull request #248260 from sunasing/sunasing-branch-4
Updating query cost throttling limits
2 parents 536cbc0 + 4a4998a commit dfe3b47

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

includes/azure-monitor-limits-metrics.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,18 @@ Based on query time range and range vectors in query over a 3-minute window (for
8787
| Query hours per Azure Monitor workspace | 2,000,000 |
8888
| Query hours per Azure tenant | 20,000,000 |
8989

90+
**Query cost throttling limits**
91+
92+
| Limit | Value |
93+
|:---|:---|
94+
| Maximum query cost per query | 15000 |
95+
| Maximum query cost for recording rules query | 3000 |
96+
97+
Query cost calculation is done as follows:
98+
99+
Query Cost = (Number of time series requested * (queried time duration in seconds / *Inferred time resolution of queried data*) ) / 5000
100+
101+
*Inferred time resolution of queried data* = Number of data points stored in any one randomly selected time series keys of queried metric / queried time duration in seconds
90102

91103
#### Alert and recording rules
92104
Prometheus alert rules and recording rules are defined in PromQL. They're performed on the managed Ruler service as part of Azure Monitor managed service for Prometheus.

0 commit comments

Comments
 (0)