Details
-
Improvement
-
Status: Reopened
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
1.
|
Cleanup customer related events in S3G logs |
|
Resolved | Duong |
2.
|
Correct logging unhandled OMException in S3G log |
|
Open | Unassigned |
3.
|
Audit bucket ACL changes |
|
Resolved | Ritesh Shukla |
4.
|
Add tests for audit log in smoke tests |
|
Open | Unassigned |