Repository navigation
docs: fix config reference links in the heavy queries guide - #7926
Merged
SungJin1212 merged 1 commit intoNov 10, 2026
Merged
SungJin1212 merged 1 commit into
SungJin1212 merged 1 commit into
Conversation
Signed-off-by: sarankumar1325 <120080287+sarankumar1325@users.noreply.github.com>
SungJin1212
approved these changes
Nov 10, 2026
SungJin1212
left a comment
SungJin1212
left a comment
Member
There was a problem hiding this comment.
Thanks for fixing it. LGTM.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does:
Fixes the config reference links in
docs/guides/protecting-cortex-from-heavy-queries.md:https://cortexmetrics.io/docs/configuration/configuration-file/:~:text=query_protection. The#is missing, so the browser asks for the path/configuration-file/:~:text=query_protection, which returns 404. It now uses#ingester_config:~:text=query_protection, matching the ingester example right above it.max_outstanding_requests_per_tenant,max_fetched_data_bytes_per_query,max_fetched_series_per_query,max_fetched_chunk_bytes_per_query) used the#query_frontend_configanchor, but these settings are inlimits_config(seedocs/configuration/config-file-reference.md). They now use#limits_config, so browsers without text-fragment support also land on the right section.I checked that the
ingester_configandlimits_configanchors exist on the published page. Docs-only change, so no tests or CHANGELOG entry.I used an AI assistant to help find and fix these links, and I checked every change myself.
Which issue(s) this PR fixes:
None, small docs fix.
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]docs/configuration/v1-guarantees.mdupdated if this PR introduces experimental flags