[
https://issues.apache.org/jira/browse/HDDS-16232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang resolved HDDS-16232.
------------------------------------
Resolution: Fixed
> Document how to enable Jersey debug logs in S3 Gateway
> ------------------------------------------------------
>
> Key: HDDS-16232
> URL: https://issues.apache.org/jira/browse/HDDS-16232
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Shuo Huang
> Assignee: Shuo Huang
> Priority: Minor
> Labels: pull-request-available
>
> After HDDS-8096, S3 Gateway redirects JUL records to SLF4J through
> SLF4JBridgeHandler.
> JUL checks the log level before a record reaches SLF4JBridgeHandler. Since
> the JUL root logger remains at INFO, setting only:
> log4j.logger.org.glassfish.jersey=DEBUG
> does not enable Jersey debug logs.
> Update ozone-site's "Enabling Debug Logs for Services" section to explain
> that both the JUL level and the log4j logger level must allow the records.
> Include a working S3 Gateway/Jersey configuration example.
> References:
> - HDDS-8096
> - https://github.com/apache/ozone/pull/11005
> -
> https://ozone.apache.org/docs/administrator-guide/configuration/logging/application-logs/#enabling-debug-logs-for-services
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
