docs: export individual dashboard panels as JSON (#7611) - #7956
docs: export individual dashboard panels as JSON (#7611)#7956florent-leborgne wants to merge 13 commits into
Conversation
AI-Assisted: OpenAI Codex (GPT-5)
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
🔍 Preview links for changed docs |
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! 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. |
AI-Assisted: OpenAI Codex (GPT-5)
AI-Assisted: OpenAI Codex (GPT-5)
AI-Assisted: OpenAI Codex (GPT-5)
AI-Assisted: OpenAI Codex (GPT-5)
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Docs review summary
Focus areas
- Style and clarity: Mostly solid; one inline comment on a list-punctuation/Oxford-comma inconsistency in the new "Export a panel as JSON" section.
- Jargon: None found — panel/control/library terms are already used consistently elsewhere on the page.
- Frontmatter and applies_to: New section-level
applies_toblock (stack: preview 9.6+,serverless: preview) is correctly placed directly under the heading with no blank line, matches the linked issue's stated availability (Stack v9.6.0 preview, Serverless preview), and doesn't conflict with the page-levelgatag since it's properly scoped to the new section. - Content type fit: Fits the existing how-to page structure; the new section follows the same pattern as sibling "Export JSON" section (intro paragraph, numbered steps, screenshot).
- Contradictions: No contradictions found against published docs or the rest of this page.
- Parent issue satisfaction: Satisfied — the PR adds the panel-level Export JSON entry point, describes the Show full configuration switch for library-linked panels, and clarifies scope differences (filters/time range) as requested in #7611.
Notes
- Pre-existing Vale warning on line 2 (
mapped_pages) is untouched by this PR and out of scope for this review.
Generated by Docs review agent for #7956 · sonnet50 · 40.5 AIC · ⌖ 6.5 AIC · ⊞ 17.1K
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Instructions are clear and LGTM, the only thing that might be helpful to add is a bit more info on the "why". The bullet at the top says "to inspect or save it", but there's not much further info in the section itself. I'm wondering what would users do with the config after they've saved it, and when it would be beneficial to export just a single panel vs the whole dashboard.
| - Visualizations created with the point-and-click editor or with an {{esql}} query | ||
| - **Links** and **Markdown** panels | ||
| - Unpinned **Options list**, **Range slider**, and **Variable** controls |
There was a problem hiding this comment.
It might be because I'm not very familiar with these concepts, but I'd find it helpful if we linked out to the pages where these are described (especially for things like "point-and-click editor", which isn't easy to find in the navigation unless you know it's part of Lens)
2 participants
Summary
Closes #7611.
Product sources reviewed: elastic/kibana#273427, elastic/kibana#281795, and current Kibana
main. Product PR #273427 merged tomainwith thev9.6.0label before the 9.6 branch cut.Validation
git diff --checkpassedapplies_to, content type, frontmatter, and link checksGenerative AI disclosure
Tool(s) and model(s) used: OpenAI Codex (GPT-5). Used to triangulate the docs issue and related product work, verify the current implementation, draft the change, and run documentation checks.