[
https://issues.apache.org/jira/browse/HDDS-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duong updated HDDS-6904:
------------------------
Description:
Customer related events, including validation errors, should be logged in Audi
logs only. The goal is to avoid a bad client to over load the s3g log and keep
s3g log purely for internal issues.
1. Customer events are sometimes logged in application log, e.g.
[here|https://github.com/duongnguyen0/ozone/blob/7c64595ee01f05a77675a3c5abf156d63378d727/hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/endpoint/BucketEndpoint.java#L250-L250].
Those events should be already logged to audit log and can be cleaned up.
2. OMExceptions (which indicates user errors?) are [sometimes logged to the
application
log|https://github.com/duongnguyen0/ozone/blob/7c64595ee01f05a77675a3c5abf156d63378d727/hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/endpoint/BucketEndpoint.java#L264-L264]
while they're sent to the audit log already. Those logs can just be removed.
was:
1. Customer events are sometimes logged in application log, e.g.
[here|https://github.com/duongnguyen0/ozone/blob/7c64595ee01f05a77675a3c5abf156d63378d727/hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/endpoint/BucketEndpoint.java#L250-L250].
Those events should be already logged to audit log and can be cleaned up.
2. OMExceptions (which indicates user errors?) are [sometimes logged to the
application
log|https://github.com/duongnguyen0/ozone/blob/7c64595ee01f05a77675a3c5abf156d63378d727/hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/endpoint/BucketEndpoint.java#L264-L264]
while they're sent to the audit log already. Those logs can just be removed.
> Cleanup customer related events in S3G logs
> -------------------------------------------
>
> Key: HDDS-6904
> URL: https://issues.apache.org/jira/browse/HDDS-6904
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Duong
> Assignee: Duong
> Priority: Major
>
> Customer related events, including validation errors, should be logged in
> Audi logs only. The goal is to avoid a bad client to over load the s3g log
> and keep s3g log purely for internal issues.
> 1. Customer events are sometimes logged in application log, e.g.
> [here|https://github.com/duongnguyen0/ozone/blob/7c64595ee01f05a77675a3c5abf156d63378d727/hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/endpoint/BucketEndpoint.java#L250-L250].
> Those events should be already logged to audit log and can be cleaned up.
> 2. OMExceptions (which indicates user errors?) are [sometimes logged to the
> application
> log|https://github.com/duongnguyen0/ozone/blob/7c64595ee01f05a77675a3c5abf156d63378d727/hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/endpoint/BucketEndpoint.java#L264-L264]
> while they're sent to the audit log already. Those logs can just be removed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
