Skip to content

Commit daaed72

Browse files
Expand and make more prominent integrations multi-space limitations (#894) (#901)
(cherry picked from commit 3e43c97) Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
1 parent 6bd5e1b commit daaed72

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

docs/en/ingest-management/integrations/install-integration-assets.asciidoc

+8-3
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,15 @@ and select an integration. You can select a category to narrow your search.
2222

2323
. Click **Install <integration> assets** to set up the {kib} and {es} assets.
2424

25-
There are a couple of things to note about installing integration assets:
25+
Note that it's currently not possible to have multiple versions of the same integration installed. When you upgrade an integration, the previous version assets are removed and replaced by the current version.
2626

27-
* {agent} integration assets can be installed only on a single {kib} {kibana-ref}/xpack-spaces.html[space]. If you want to access assets in a different space, you can {kibana-ref}/managing-saved-objects.html#managing-saved-objects-copy-to-space[copy them]. We recommend reviewing the specific integration documentation for any space-related considerations.
28-
* It's currently not possible to have multiple versions of the same integration installed. When you upgrade an integration, the previous version assets are removed and replaced by the current version.
27+
[IMPORTANT]
28+
.Current limitations with integrations and {kib} spaces
29+
====
30+
{agent} integration assets can be installed only on a single {kib} {kibana-ref}/xpack-spaces.html[space]. If you want to access assets in a different space, you can {kibana-ref}/managing-saved-objects.html#managing-saved-objects-copy-to-space[copy them]. However, many integrations include markdown panels with dynamically generated links to other dashboards. When assets are copied between spaces, these links may not behave as expected and can result in a 404 `Dashboard not found` error. Refer to known issue {kibana-issue}175072[#175072] for details.
31+
32+
These limitations and future plans for {fleet}'s integrations support in multi-space environments are currently being discussed in {kibana-issue}175831[#175831]. Feedback is very welcome. For now, we recommend reviewing the specific integration documentation for any space-related considerations.
33+
====
2934

3035
[discrete]
3136
[[uninstall-integration-assets]]

0 commit comments

Comments
 (0)