docs: document linked vs. dashboard-only panels and library compatibility (#6124)#6567
Draft
florent-leborgne wants to merge 1 commit into
Draft
docs: document linked vs. dashboard-only panels and library compatibility (#6124)#6567florent-leborgne wants to merge 1 commit into
florent-leborgne wants to merge 1 commit into
Conversation
…lity (#6124) Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
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. |
Contributor
🔍 Preview links for changed docs |
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. |
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
1 participant
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
This PR addresses #6124 with the following changes:
explore-analyze/visualize/manage-panels.md: Added a new "Linked panels and dashboard-only panels" section explaining the two panel states, their implications (edit propagation, data loss risk), and how to transition between them. Expanded the one-liner about Unlink from library into a full explanation of what it does, what remains unchanged in the library, and when to use it.explore-analyze/visualize/visualize-library.md: Added a new "Panel types compatible with the Visualize Library" section listing which panel types support the library (Lens, ES|QL, Maps, Vega, Discover sessions, legacy types) and which are always dashboard-only (ML panels, SLO panels, Alerts, layout elements).explore-analyze/visualize.md: Added a Visualize Library column to the panel type table so users can see at a glance whether each panel type can be saved as a shared library object. Added an intro sentence cross-linking to the new conceptual section. Updated the Discover sessions row description to accurately reflect that sessions are saved as shared objects (the previous wording implied they were always dashboard-only).Resolves
Closes #6124