HDDS-16232. Document how to enable Jersey debug logs in S3 Gateway - #533
Merged
Conversation
jojochuang
approved these changes
Aug 20, 2026
jojochuang
marked this pull request as ready for review
August 20, 2026 16:31
Contributor
|
Merged. Thanks @F64116045 |
Contributor
Author
|
Thanks @jojochuang for the review |
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.
What changes were proposed in this pull request?
HDDS-8096 (apache/ozone#11005) redirects Jersey logs from JUL to SLF4J so they are written to the S3 Gateway log file.
JUL checks the log level before a record reaches
SLF4JBridgeHandler. Therefore, setting onlylog4j.logger.org.glassfish.jersey=DEBUGdoes not enable Jersey debug logs.This change documents how to set the Jersey JUL logger to
FINE, enable itsDEBUGlevel in log4j, and load the JUL configuration when starting S3 Gateway.What is the link to the Apache Jira?
https://issues.apache.org/jira/browse/HDDS-16232
How was this patch tested?
pnpm exec markdownlint docs/05-administrator-guide/02-configuration/02-logging/01-application-logs.mdpnpm buildFINErecord reaches reload4j only when JUL is set toFINEand log4j is set toDEBUG.