[Elasticsearch]: Docs table and query analytics dashboard#18905
Merged
consulthys merged 2 commits intoMay 9, 2026
Conversation
…tables Pipe characters in descriptions broke the exported-fields Markdown table. Use HTML entity | for the separator so cells stay aligned while still rendering as ES|QL. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Vale Linting ResultsSummary: 1 suggestion found 💡 Suggestions (1)
The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
…h panel - Replace discover_session embeddable with saved search panel (fixes missing Discover session tab after package install). - Move remote-cluster section panels and controls to bottom grid rows after section metadata was removed for older Kibana compatibility. Co-authored-by: Cursor <cursoragent@cursor.com>
consulthys
changed the title
pickypg
approved these changes
May 9, 2026
consulthys
changed the title
consulthys
added
Integration:elasticsearch
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
audit |
3412.97 | 1078.75 | -2334.22 (-68.39%) | 💔 |
deprecation |
6024.1 | 4854.37 | -1169.73 (-19.42%) | 💔 |
slowlog |
8064.52 | 5208.33 | -2856.19 (-35.42%) | 💔 |
To see the full report comment with /test benchmark fullreport
💚 Build Succeeded
cc @consulthys |
|
Package elasticsearch - 1.21.1 containing this change is available at https://epr.elastic.co/package/elasticsearch/1.21.1/ |
3 tasks
andrewkroh
added
dashboard
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
4 participants
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
Relates to #13374
Follow-up fixes for the Elasticsearch integration querylog work (integrations#18859):
ES|QLbroke Markdown table columns in the generated field reference.sections, etc.), some panels kept section-relative grid coordinates (y: 0/y: 2) and appeared at the top of the dashboard instead of the bottom. The Historical queries panel used adiscover_sessionembeddable tied to a Discover tab id that is not portable with the package, which triggered “The Discover session tab saved with this panel no longer exists” after install.Changes
Documentation
ES|QLwithES|QLindata_stream/querylog/fields/fields.ymldescriptions (renders as ES|QL without splitting Markdown table cells).docs/README.mdviaelastic-package build.Query analytics dashboard (
kibana/dashboard/elasticsearch-query-analytics-dashboard.json)discover_sessionwith asearchembeddable (panelRefName:savedObjectRef) so Historical queries uses the packaged saved searchelasticsearch-5df8f5ab-0459-4c89-95b4-3b3d235386bdinstead of an ephemeral Discover session id.y91+ / 93+) so layout matches the intended order below the main charts.Testing
elastic-package check(lint + package build / README render)cc @elastic/stack-monitoring