Update default logging configurations for Kafka brokers and MM2 #10961
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.
Type of change
Description
This PR updates the logging configuration for Kafka brokers/controllers and MM2 to bring it in-sync with Kafka's own default configuration. This helps to avoid confusion among users why are they seeing some TRACE messages in the Kafka logs from Strimzi when they did not enable them.
(While Kafka 4.0 will have a new logging configuration based on Log4j2, this will be still useful for Kafka 3.9.0)
Checklist