Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Fleet managed integrations content #970

Merged
merged 3 commits into from
Mar 25, 2024
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 2 additions & 0 deletions docs/en/ingest-management/index.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -209,6 +209,8 @@ include::integrations/view-integration-assets.asciidoc[leveloffset=+2]

include::integrations/upgrade-integration.asciidoc[leveloffset=+2]

include::integrations/managed-integrations-content.asciidoc[leveloffset=+2]

include::data-streams.asciidoc[leveloffset=+2]

include::processors/processors.asciidoc[leveloffset=+1]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -61,3 +61,4 @@ The *Integrations* app in {kib} needs access to the public {package-registry} to
discover integrations. If your deployment has network restrictions, you can
{fleet-guide}/air-gapped.html#air-gapped-diy-epr[deploy your own self-managed {package-registry}].
====

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd maybe remove this extra line just to avoid including an extra file in the PR.

Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
[[managed-integrations-content]]
= Managed integrations content

++++
<titleabbrev>Managed integrations content</titleabbrev>
++++

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::images/system-managed.png[An image of the new managed badge.]

The cloned content is unlinked with the original reference configurations, so becomes independent from the original managed content. 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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The cloned content is unlinked with the original reference configurations, so becomes independent from the original managed content.

I don't think we can call this a general rule. For example, a managed visualization may use the logs-* data view which is a managed data view. And the cloned version will, too.

The only case where the unlinking happens is with dashboard panels, as you've described here!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah ok, sorry that was a bad assumption. Let me rework this and also update the corresponding Kibana page.


[NOTE]
====
The cloned managed content retains the managed badge, but is independent from the original.
====