[docs-agent] Document discover:defaultEsqlQuery advanced setting - #7865
Closed
github-actions[bot] wants to merge 1 commit into
Closed
[docs-agent] Document discover:defaultEsqlQuery advanced setting#7865github-actions[bot] wants to merge 1 commit into
discover:defaultEsqlQuery advanced setting#7865github-actions[bot] wants to merge 1 commit into
Conversation
Adds a subsection to Use ES|QL in the Kibana UI explaining the discover:defaultEsqlQuery space-level advanced setting, which lets users override the data-source-derived default ES|QL query in Discover, including validation, scope, and priority behavior. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
|
Test of the github action Overall: the steps are correct with a few caveats:
What I implement instead: #7869 |
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.
Adds a "Set a default query" subsection to Use ES|QL in the Kibana UI, under Manage queries, documenting the new
discover:defaultEsqlQueryspace-level advanced setting: how to set it, its scope, syntax-only validation, when it stops applying, and its priority against a Discover-profile default and the data-source-derived query.Triage rationale: The issue and linked Kibana PR elastic/kibana#281319 (closing elastic/kibana#281180) together fully specify the behavior: the setting name, its priority order, its syntax-only validation, and that it doesn't apply after a user edits the query or switches modes. The auto-generated advanced settings reference already lists the setting, so this narrative mention was the only missing piece, making the task sufficiently scoped for autonomous handling.
Drafting sources:
explore-analyze/query-filter/languages/esql-kibana.mdandexplore-analyze/discover/try-esql.md(canonical page and terminology/placement)(reference/redacted) (existing auto-generated reference link pattern used elsewhere on the page, e.g. fordateFormat:tzanddiscover:sampleSize`)contribute-docs/style guide and cumulative-docs/applies_to conventionsReader test: Reader goal — a Kibana admin wanting to override Discover's derived ES|QL query with their own default. 2 rounds. Round 1 surfaced three blocking gaps: no steps for locating the setting, unclear scope of "validates syntax only," and an undefined "Discover session profile" term with no canonical page to link. Round 2 added explicit navigation steps, clarified that syntax-only validation doesn't check whether the query returns results, and replaced the unlinkable term with "a Discover profile provided by your organization." No blocking gaps remained after round 2.
Closes #7695
This draft PR was produced autonomously by docs-agent-experimental in experimental mode.
Safe-output PRs do not trigger CI by default. A maintainer must trigger the required checks manually.