[HADOOP-18183] s3a audit logs to publish range start/end of GET requests in audit header

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.3.2
• Fix Version/s: 3.4.0, 3.3.9
• Component/s: fs/s3
• Labels: pull-request-available
• Target Version/s: 3.3.9
• Hadoop Flags: Reviewed
• Assignee: Ankit Saurabh
• Reporter: Steve Loughran
• Created: 28/Mar/22 17:17
• Updated: 28/Jan/24 08:29
• Resolved: 31/Jul/23 16:39

Description

we don't get the range of ranged get requests in s3 server logs, because the AWS s3 log doesn't record that information. we can see it's a partial get from the 206 response, but the length of data retrieved is lost.

LoggingAuditor.beforeExecution() would need to recognise a ranged GET and determine the extra key-val pairs for range start and end (rs & re?)

we might need to modify HttpReferrerAuditHeader.buildHttpReferrer() to take a map of <string, string> so it can dynamically create a header for each request; currently that is not in there.

Issue Links

• links to: GitHub Pull Request #5110
• links to: GitHub Pull Request #5218