Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update default logging configurations for Kafka brokers and MM2 #10961

Merged
merged 1 commit into from
Dec 17, 2024

Conversation

scholzj
Copy link
Member

@scholzj scholzj commented Dec 17, 2024

Type of change

  • Task

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

  • Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally

@scholzj scholzj added this to the 0.46.0 milestone Dec 17, 2024
@scholzj scholzj requested a review from a team December 17, 2024 09:54
@katheris
Copy link
Contributor

Should we also update the changelog.md in case some users are relying on the trace log lines for some reason?

@scholzj
Copy link
Member Author

scholzj commented Dec 17, 2024

/azp run regression

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@scholzj scholzj merged commit 7226ab8 into strimzi:main Dec 17, 2024
21 checks passed
@scholzj scholzj deleted the update-default-logging-configurations branch December 17, 2024 22:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants