Skip to content

Commit

Permalink
[8.13] [DOCS] Fleet managed content (#178380) (#179393)
Browse files Browse the repository at this point in the history
# Backport

This will backport the following commits from `main` to `8.13`:
- [[DOCS] Fleet managed content
(#178380)](#178380)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"amyjtechwriter","email":"61687663+amyjtechwriter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-03-25T22:14:29Z","message":"[DOCS]
Fleet managed content (#178380)\n\n## Summary\r\n\r\nThe
[Fleet\r\npage](https://www.elastic.co/guide/en/kibana/current/fleet.html)
in the\r\nKibana docs needed to be updated to reflect that most
Fleet-installed\r\nintegrations cannot be directly edited any longer.
Users need to make\r\nclones of this managed content to make edits and
customizations.\r\n\r\nCloses:
[#175150](https://github.com/elastic/kibana/issues/175150)\r\n\r\nRelates
to:
[#970](https://github.com/elastic/ingest-docs/pull/970)","sha":"ab98a258b262a3fe3bb6a9a6b56e3d9d9021a1c3","branchLabelMapping":{"^v8.14.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.13.0","v8.14.0"],"title":"[DOCS]
Fleet managed
content","number":178380,"url":"https://github.com/elastic/kibana/pull/178380","mergeCommit":{"message":"[DOCS]
Fleet managed content (#178380)\n\n## Summary\r\n\r\nThe
[Fleet\r\npage](https://www.elastic.co/guide/en/kibana/current/fleet.html)
in the\r\nKibana docs needed to be updated to reflect that most
Fleet-installed\r\nintegrations cannot be directly edited any longer.
Users need to make\r\nclones of this managed content to make edits and
customizations.\r\n\r\nCloses:
[#175150](https://github.com/elastic/kibana/issues/175150)\r\n\r\nRelates
to:
[#970](https://github.com/elastic/ingest-docs/pull/970)","sha":"ab98a258b262a3fe3bb6a9a6b56e3d9d9021a1c3"}},"sourceBranch":"main","suggestedTargetBranches":["8.13"],"targetPullRequestStates":[{"branch":"8.13","label":"v8.13.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.14.0","branchLabelMappingKey":"^v8.14.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/178380","number":178380,"mergeCommit":{"message":"[DOCS]
Fleet managed content (#178380)\n\n## Summary\r\n\r\nThe
[Fleet\r\npage](https://www.elastic.co/guide/en/kibana/current/fleet.html)
in the\r\nKibana docs needed to be updated to reflect that most
Fleet-installed\r\nintegrations cannot be directly edited any longer.
Users need to make\r\nclones of this managed content to make edits and
customizations.\r\n\r\nCloses:
[#175150](https://github.com/elastic/kibana/issues/175150)\r\n\r\nRelates
to:
[#970](https://github.com/elastic/ingest-docs/pull/970)","sha":"ab98a258b262a3fe3bb6a9a6b56e3d9d9021a1c3"}}]}]
BACKPORT-->

Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com>
  • Loading branch information
kibanamachine and amyjtechwriter authored Mar 25, 2024
1 parent 7bf3f64 commit 4b22c83
Show file tree
Hide file tree
Showing 2 changed files with 21 additions and 0 deletions.
21 changes: 21 additions & 0 deletions docs/fleet/fleet.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,27 @@ It is recommended for advanced users only.
[role="screenshot"]
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 (&#8801;) 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]
== Get started

Expand Down
Binary file added docs/fleet/images/system-managed.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 4b22c83

Please sign in to comment.