Repository navigation
[8.19.x] Use the UI label Custom Query for the SLO indicator type - #4986
Merged
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
🤖 GitHub commentsJust comment with:
|
vishaangelova
approved these changes
Nov 9, 2026
Contributor
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
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.
Summary
Updates the 8.19 Create an SLO page to use the UI name Custom Query for the first SLI type. Kibana renamed the label from "Custom KQL" in 8.14 (elastic/kibana#179497), and the 8.19 docs still use the old name.
The change covers the bullet link text, the section heading, and the two body mentions. The
custom-kql-slianchor stays, so existing links keep working.Relates to elastic/docs-content#9278, which tracks the same fix on the current docs (elastic/docs-content#9279).