[UII] Add remote cluster instructions for syncing integrations #211997
Conversation
jen-huang
added
release_note:fix
backport:skip
|
Pinging @elastic/fleet (Team:Fleet) |
| <EuiSpacer size="m" /> | ||
| <FormattedMessage | ||
| id="xpack.fleet.settings.remoteClusterConfiguration.description" | ||
| defaultMessage="The Remote Elasticsearch output must have additional configuration to sync integrations from this cluster. {documentationLink}." |
There was a problem hiding this comment.
@kilfoyle I would appreciate some wordsmithing magic on all the text added in this callout :) There's sort of a two-way "remote cluster" situation which I found hard to explain.
The user is setting up a "remote Elasticsearch" output on this local cluster. In order to automatically sync integration assets to that remote ES, we need them to connect this local cluster to that remote cluster. From that cluster's perspective, this local cluster is considered the "remote cluster." Does it make sense? 😅
There was a problem hiding this comment.
Sure! How about this? Just some slight changes from the original. For the third step, to shorten it a bit I suppose we can omit the "allow this cluster to read integration status" as they'll gather what it's for.
To sync integrations from this cluster, the remote Elasticsearch output needs additional configuration. [Learn more ↗.]
In the remote cluster, open Kibana and go to Stack Management > Remote Clusters, and follow the steps to add this cluster.
Go to Stack Management > Cross-Cluster Replication and create a follower index using the cluster from Step 1. The leader index
fleet-synced-integrationsfrom this cluster should be replicated to the follower indexfleet-synced-integrations-ccr-<output name>on the remote cluster.Below, provide the access details for the remote cluster's Kibana instance.
| defaultMessage="The Remote Elasticsearch output must have additional configuration to sync integrations from this cluster. {documentationLink}." | ||
| values={{ | ||
| documentationLink: ( | ||
| <EuiLink external={true} href={docLinks.links.fleet.remoteESOoutput}> |
There was a problem hiding this comment.
Yup! That makes sense to me. Best to keep all the remote ES stuff together on the same page.
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
Page load bundle
History
cc @jen-huang |
Summary
Resolves #206239. This PR adds instructions for configuring the remote cluster to enable syncing integrations (for a Remote Elasticsearch output).
It also hides extra fields when
Sync integrationsis not enabled:When enabled:
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.