[
https://issues.apache.org/jira/browse/HDDS-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ritesh H Shukla reopened HDDS-6559:
-----------------------------------
We should make sure that all customer triggered logging is sent to audit log.
# Success/Failure
# Invalid parameters
# Vol/Bucket/Objects not found
# Access permission failures
The goal is to avoid a bad client to over load the s3g log and keep s3g log
purely for internal issues.
> 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
> Assignee: Duong
> 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: [email protected]
For additional commands, e-mail: [email protected]
