[
https://issues.apache.org/jira/browse/HADOOP-17511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-17511:
------------------------------------
Description:
Add a way for auditing tools to correlate S3 object calls with Hadoop FS API
calls.
Initially just to log/forward to an auditing service.
Later: let us attach them as parameters in S3 requests, such as opentrace
headeers or (my initial idea: http referrer header -where it will get into the
log)
Challenges
* ensuring the audit span is created for every public entry point. That will
have to include those used in s3guard tools, some defacto public APIs
* and not re-entered for active spans. s3A code must not call back into the FS
API points
* Propagation across worker threads
Documentation Links
* Using:
https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/auditing.md
* architecture:
https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/auditing_architecture.md
was:
Add a way for auditing tools to correlate S3 object calls with Hadoop FS API
calls.
Initially just to log/forward to an auditing service.
Later: let us attach them as parameters in S3 requests, such as opentrace
headeers or (my initial idea: http referrer header -where it will get into the
log)
Challenges
* ensuring the audit span is created for every public entry point. That will
have to include those used in s3guard tools, some defacto public APIs
* and not re-entered for active spans. s3A code must not call back into the FS
API points
* Propagation across worker threads
> Add an Audit plugin point for S3A auditing/context
> --------------------------------------------------
>
> Key: HADOOP-17511
> URL: https://issues.apache.org/jira/browse/HADOOP-17511
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 3.3.1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.3.2
>
> Time Spent: 22h 20m
> Remaining Estimate: 0h
>
> Add a way for auditing tools to correlate S3 object calls with Hadoop FS API
> calls.
> Initially just to log/forward to an auditing service.
> Later: let us attach them as parameters in S3 requests, such as opentrace
> headeers or (my initial idea: http referrer header -where it will get into
> the log)
> Challenges
> * ensuring the audit span is created for every public entry point. That will
> have to include those used in s3guard tools, some defacto public APIs
> * and not re-entered for active spans. s3A code must not call back into the
> FS API points
> * Propagation across worker threads
> Documentation Links
> * Using:
> https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/auditing.md
> * architecture:
> https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/auditing_architecture.md
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
