Update graceful handling for missing indices to accommodate the new fleet system indices plugin #205
Conversation
This file contains 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
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
mergify bot
added a commit
that referenced
this pull request
Apr 13, 2021
…leet system indices plugin (#205) (#231) * Update the no index found handling to accommodate the new fleet system indices plugin * Add logging (cherry picked from commit 85d0ebf) Co-authored-by: Aleksandr Maus <[email protected]>
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.
What does this PR do?
Graceful handling for the case where the indices are not found.
Tested full stack with ES system indices plugin PR elastic/elasticsearch#70689
and kibana update for this elastic/kibana#96338 working end to end with osquerybeat.
Found issues where fleet server doesn't handle the case where the index doesn't exists.
The ES system indices plugin no longer creates the indices. The indices are now created when the first document is pushed, and the fleet server doesn't handle the missing index case gracefully (as some point before it did).
This change can be merged before the related tickets.
Why is it important?
This is important in order to adopt the fleet system indices plugin.
Checklist