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-metrics.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,6 +87,18 @@ Based on query time range and range vectors in query over a 3-minute window (for
87
87
| Query hours per Azure Monitor workspace | 2,000,000 |
88
88
| Query hours per Azure tenant | 20,000,000 |
89
89
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
90
102
91
103
#### Alert and recording rules
92
104
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