[Kafka] Add support for Kafka 4.1.1 logs#19244
Open
Alphayeeeet wants to merge 4 commits into
Open
Conversation
ReviewersBuildkite won't run for external contributors automatically; you need to add a comment:
NOTE: https://github.com/elastic/integrations/blob/main/.buildkite/pull-requests.json contains all those details. |
andrewkroh
added
documentation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Please label as enhancement
Extended grok patterns to support Kafka 4.1.1 logs.
As test data, logs written by the Strimzi Operator on version 0.51.0 running Kafka 4.1.1 were used:
Therefore the grok pattern might differ for other Kafka operators depending on their default log pattern settings.
However as Strimzi is a well-known Kafka management operator, we would wish to include support for their default log pattern in the generic integration, as we think providing out of the box support is a benefit for everyone using this.
The support has been added in a backward compatible manner so no side effects to current deployments are expected.