Summary
Dashboard authors can now populate Options list and Range slider filter controls from an ES|QL query instead of selecting a data view field directly. The Create control flyout adds a Select a field / Write a query input toggle; the query path runs an ES|QL query to derive the control field and limits the values shown (options list) or the min/max bounds (range slider). This helps high-cardinality fields that slow dashboards when Kibana fetches all distinct values, and supports chaining with ES|QL variable controls by referencing ?variable syntax in the values query.
Why this needs docs: The PR adds substantial public UI in the controls plugin (data_control_editor, configure_values_query) with verified i18n labels, but the add-controls how-to still documents only the data-view-and-field workflow.
Resources
Screenshots from PR
Availability
| Channel |
Details |
| Stack |
v9.5.0 |
| Serverless |
Jun 29–Jul 3 |
| Feature flag |
None — active by default |
Created with Docs Quest Scanner by @florent-leborgne
Suggested edits
Add filter controls > Create and add Options list and Range slider controls
- What the docs say: Steps 3–4 instruct authors to pick a Data view and Field, then choose Options list or Range slider under Control type. No mention of an ES|QL-based values source or pre-filtering possible values.
- What to add: Add a version-scoped subsection (preserve the existing field-based steps for earlier stacks) documenting the Write a query input option: write and Run query an ES|QL query that returns a single column (via
STATS BY or similar), preview possible values, and save; explain that range sliders derive min/max from query results and that queries can reference dashboard ES|QL variable controls (?variable_name) to chain filtering. Note that the values preview appears only after the query runs, and that multi-column or empty results show editor error states. Update workflow screenshots for the create-control flyout. Applies from 9.5.0 and in serverless.
TriageBot — Complete
2026-06-26
Type: documentation
Section check:
- ✅ Problem statement: clearly explains the missing coverage and why it's needed
- ✅ Proposed outcome: "Suggested edits" section provides specific, actionable instructions
Cross-references:
Next step: none — issue is complete
Generated by Gh Aw Issue Triage for issue #7130 · 30.6 AIC · ⌖ 7.9 AIC · ⊞ 9.1K · ◷
Summary
Dashboard authors can now populate Options list and Range slider filter controls from an ES|QL query instead of selecting a data view field directly. The Create control flyout adds a Select a field / Write a query input toggle; the query path runs an ES|QL query to derive the control field and limits the values shown (options list) or the min/max bounds (range slider). This helps high-cardinality fields that slow dashboards when Kibana fetches all distinct values, and supports chaining with ES|QL variable controls by referencing
?variablesyntax in the values query.Why this needs docs: The PR adds substantial public UI in the controls plugin (
data_control_editor,configure_values_query) with verified i18n labels, but the add-controls how-to still documents only the data-view-and-field workflow.Resources
Screenshots from PR
Availability
Created with Docs Quest Scanner by
@florent-leborgneSuggested edits
Add filter controls > Create and add Options list and Range slider controls
STATS BYor similar), preview possible values, and save; explain that range sliders derive min/max from query results and that queries can reference dashboard ES|QL variable controls (?variable_name) to chain filtering. Note that the values preview appears only after the query runs, and that multi-column or empty results show editor error states. Update workflow screenshots for the create-control flyout. Applies from 9.5.0 and in serverless.TriageBot — Complete
2026-06-26
Type: documentation
Section check:
Cross-references:
Next step: none — issue is complete