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: website/content/en/blog/2025/query-rejection.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ Think of query rejection as an “emergency stop” in a factory. It sits in fro
38
38
39
39
Heavy queries often share identifiable traits. Query rejection lets you match on a variety of attributes and reject only those requests. You can combine as many of these as needed:
40
40
41
-
-**API type:**`query`, `query_range`, `series`, etc.
41
+
-**API type:**`query`, `query_range`. For now, query rejection only applies to these two API types.
42
42
-**Query string (regex):** Match by pattern, e.g., any query containing “ALERT”.
43
43
-**Time range:** Match queries whose range falls between a configured **min** and **max**.
44
44
-**Time window:** Match queries based on how far their time window is from now by specifying relative **min** and **max** boundaries. This is often used to distinguish queries that hit hot storage versus cold storage.
0 commit comments