Skip to content

Commit 821304f

Browse files
authored
Update query rejection blog post to reflect what api_types it currently supports (#7044)
Signed-off-by: Erlan Zholdubai uulu <[email protected]>
1 parent 126926b commit 821304f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

website/content/en/blog/2025/query-rejection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Think of query rejection as an “emergency stop” in a factory. It sits in fro
3838

3939
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:
4040

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.
4242
- **Query string (regex):** Match by pattern, e.g., any query containing “ALERT”.
4343
- **Time range:** Match queries whose range falls between a configured **min** and **max**.
4444
- **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

Comments
 (0)