Skip to content

Update query rejection blog post to reflect what api_types it current… #7044

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 3, 2025
Merged

Update query rejection blog post to reflect what api_types it current… #7044

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/content/en/blog/2025/query-rejection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Think of query rejection as an “emergency stop” in a factory. It sits in fro

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:

- **API type:** `query`, `query_range`, `series`, etc.
- **API type:** `query`, `query_range`. For now, query rejection only applies to these two API types.
- **Query string (regex):** Match by pattern, e.g., any query containing “ALERT”.
- **Time range:** Match queries whose range falls between a configured **min** and **max**.
- **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.
Expand Down
Loading