Support elastic_data_stream #1190
Merged
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
Signed-off-by: Fabian Schlager <fabian.schlager@advastore.com>
fschlager
force-pushed
the
feat/elastic-data-stream
branch
from
742289e
to
b395c4b
Compare
benjaminhuo
approved these changes
Jun 4, 2024
|
@fschlager Thanks, that's big enhancement! |
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 this PR does / why we need it:
This PR adds support for Elasticsearch's data streams:
The underlying fluentd plugin already supports this, with this PR we can make use of it in the usual fluent-operator context.
This is designed to be a separate plugin to keep things simple, to reflect how this is treated by fluentd itself and to not break existing configurations.
Which issue(s) this PR fixes:
Fixes #1170
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: