mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 18:51:07 -04:00
[DOCS] Fleet managed content (#178380)
## Summary The [Fleet page](https://www.elastic.co/guide/en/kibana/current/fleet.html) in the Kibana docs needed to be updated to reflect that most Fleet-installed integrations cannot be directly edited any longer. Users need to make clones of this managed content to make edits and customizations. Closes: [#175150](https://github.com/elastic/kibana/issues/175150) Relates to: [#970](https://github.com/elastic/ingest-docs/pull/970)
This commit is contained in:
parent
37bd29d48f
commit
ab98a258b2
2 changed files with 21 additions and 0 deletions
|
@ -18,6 +18,27 @@ It is recommended for advanced users only.
|
||||||
[role="screenshot"]
|
[role="screenshot"]
|
||||||
image::fleet/images/fleet-start.png[{fleet} app in {kib}]
|
image::fleet/images/fleet-start.png[{fleet} app in {kib}]
|
||||||
|
|
||||||
|
Most integration content installed by {fleet} isn’t editable. This content is tagged with a **Managed** badge in the {kib} UI. Managed content itself cannot be edited or deleted, however managed visualizations, dashboards, and saved searches can be cloned.
|
||||||
|
|
||||||
|
[role="screenshot"]
|
||||||
|
image::fleet/images/system-managed.png[An image of the new managed badge.]
|
||||||
|
|
||||||
|
When a managed dashboard is cloned, any linked or referenced panels become part of the clone without relying on external sources. The panels are integrated into the cloned dashboard as stand alone components. For example, with a cloned dashboard, the cloned panels become entirely self-contained copy without any dependencies on the original configuration. Clones can be customized and modified without accidentally affecting the original.
|
||||||
|
|
||||||
|
NOTE: The cloned managed content retains the managed badge, but is independent from the original.
|
||||||
|
|
||||||
|
You can make a complete clone of a whole managed dashboard. If you clone a panel within a managed dashboard, you're prompted to save the changes as a new dashboard, which is unlinked from the original managed content.
|
||||||
|
|
||||||
|
To clone a dashboard:
|
||||||
|
|
||||||
|
. Open the main menu (≡) and click *Dashboards*.
|
||||||
|
. Click on the name of the managed dashboard to view the dashboard.
|
||||||
|
. Click *Clone* in the toolbar.
|
||||||
|
. Click *Save and return* after editing the dashboard.
|
||||||
|
. Click *Save*.
|
||||||
|
|
||||||
|
To clone managed content relating to specific visualization editors, such as Lens, TSVB, and Maps, view the visualization in the editor then begin to make edits. Unlike cloning dashboards, and dashboard panels, the cloned content retains the original configurations. Once finished you are prompted to save the edits as a new visualization. The same applies for altering any saved searches in a managed visualization.
|
||||||
|
|
||||||
[float]
|
[float]
|
||||||
== Get started
|
== Get started
|
||||||
|
|
||||||
|
|
BIN
docs/fleet/images/system-managed.png
Normal file
BIN
docs/fleet/images/system-managed.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 221 KiB |
Loading…
Add table
Add a link
Reference in a new issue