[Fleet] unhealthy remote ES warning can be ignored #1307
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kilfoyle
changed the title
lucabelluccini
approved these changes
Apr 29, 2025
There was a problem hiding this comment.
Hello @kilfoyle - thanks for the update! For me it's good. Idk if this has to be seen by Nima and/or Kyle?
|
@juliaElastic does adding this warning look okay to you? If I recall correctly you worked on the remote ES feature. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a note to the Fleet "Remote Elasticsearch Output" page indicating that warning about unhealthy state can be ignored in cases where Fleet Server can't connect to the remote cluster used only for agent data.
Please see: Docs preview
Closes: #1201