Skip to content

Conversation

jillguyonnet
Copy link
Contributor

@jillguyonnet jillguyonnet commented Apr 16, 2025

Closes elastic/kibana#208946

This PR updates the documentation about remote Elasticsearch outputs with:

  • a mention of the feature to sync uninstalled integrations
  • a new troubleshooting section

Screenshots

Screenshot 2025-04-17 at 10 06 32 Screenshot 2025-04-17 at 10 06 46 Screenshot 2025-04-17 at 10 07 10

@jillguyonnet jillguyonnet self-assigned this Apr 16, 2025
@jillguyonnet
Copy link
Contributor Author

Hi @juliaElastic @criamico This is a first draft based on my current understanding and UI designs. Please let me know if I left anything out.

@kilfoyle FYI while this is in draft.

@criamico
Copy link

Should we mention that the remote cluster needs to have an elasticsearch output configured matching the remote_elasticsearch output in the main one? I recall some discussion about it but I don't know what was the outcome.

If this condition is necessary to kickstart the sync, I think it should be mentioned in the troubleshooting section.

@jillguyonnet
Copy link
Contributor Author

Should we mention that the remote cluster needs to have an elasticsearch output configured matching the remote_elasticsearch output in the main one? I recall some discussion about it but I don't know what was the outcome.

I had asked the same question in #952 (comment). As I understand, the default output takes care of that as its host URL should match that of the remote output, so there is no further action needed from the user. In our local dev setup, we need to alter the port of the default output to make it work, but this seems like a very specific case.

@juliaElastic
Copy link
Contributor

I had asked the same question in #952 (comment). As I understand, the default output takes care of that as its host URL should match that of the remote output, so there is no further action needed from the user. In our local dev setup, we need to alter the port of the default output to make it work, but this seems like a very specific case.

Yes the default ES output should take care of this, we could mention it in the docs, something like: "Check that the remote Elasticsearch host is correct (should match one of the Elasticsearch hosts on the remote cluster)"

@jillguyonnet jillguyonnet marked this pull request as ready for review April 16, 2025 12:25
@jillguyonnet jillguyonnet requested a review from kilfoyle April 16, 2025 12:26
Copy link
Contributor

@juliaElastic juliaElastic left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@kilfoyle kilfoyle left a comment

Choose a reason for hiding this comment

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

LGTM! ⛵
Just a few super minor suggestions. Thanks a lot @jillguyonnet for adding these nice docs!

@jillguyonnet jillguyonnet enabled auto-merge (squash) April 17, 2025 08:12
@jillguyonnet jillguyonnet merged commit 63768bf into elastic:main Apr 17, 2025
3 of 4 checks passed
@jillguyonnet jillguyonnet deleted the fleet-add-integration-sync-troubleshooting branch April 17, 2025 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Fleet] Add doc to troubleshoot sync integration errors

4 participants