Use separate logger for Jetty in Topic Operator #9468
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: Jakub Scholz <[email protected]>
ppatierno
approved these changes
Dec 15, 2023
scholzj
changed the title
scholzj
added a commit
that referenced
this pull request
Dec 18, 2023
Signed-off-by: Jakub Scholz <[email protected]>
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.
Type of change
Description
This PR adds a separate logger for Jetty in the logging configurations of the Topic Operator. That helps to make sure that when the user enables the DEBUG logging for the root logger of the TO, Jetty will by default stay at the INFO level. This helps to reduce the number of messages that do not seem very useful such as the various Jetty threading logs etc.
This contributes to #9465 (but does not address all parts of it).
Checklist