You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Ritesh H Shukla (Jira)" <ji...@apache.org> on 2022/04/19 20:33:00 UTC

[jira] [Commented] (HDDS-6559) S3G client logging review

    [ https://issues.apache.org/jira/browse/HDDS-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524576#comment-17524576 ] 

Ritesh H Shukla commented on HDDS-6559:
---------------------------------------

With S3G audit log, the request processing details can be logged there HDDS-6525

> S3G client logging review
> -------------------------
>
>                 Key: HDDS-6559
>                 URL: https://issues.apache.org/jira/browse/HDDS-6559
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: S3
>            Reporter: Ritesh H Shukla
>            Priority: Major
>
> Currently a broad range of errors get logged to S3G's log which include errors that can be induced by a client. Ideally these should not be logged (Example invalid header), there can be an access log which only captures HTTP requests and responses but the S3G log should be for the internal state of S3G.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org