Add logging for KafkaProducer #5701
Open
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
The log message now does not contain the kafka message body itself, since it might be too big for kibana. Now along with the other information the log contains the message symbol length.
pablomuri
approved these changes
Aug 1, 2024
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.
The log message now does not contain the kafka message body itself, since it might be too big for kibana and as result we can not see the log in the elk stack. Now along with the other information the log contains the message symbol length.
basically I rolled back the logging to the previous state, but now it also logs the message symbol length for the json body.
Fix for the initial issue, related to way big message size in kafka will be in different PR as a separate task.