From a37c9578419676d1900f9002b3f4f40210ab53cf Mon Sep 17 00:00:00 2001 From: Erlan Zholdubai uulu Date: Wed, 1 Oct 2025 14:08:57 -0700 Subject: [PATCH] Update query rejection blog post to reflect what api_types it currently supports Signed-off-by: Erlan Zholdubai uulu --- website/content/en/blog/2025/query-rejection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/en/blog/2025/query-rejection.md b/website/content/en/blog/2025/query-rejection.md index 7118165ea2d..161c21139eb 100644 --- a/website/content/en/blog/2025/query-rejection.md +++ b/website/content/en/blog/2025/query-rejection.md @@ -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.