You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/02/02 16:27:01 UTC

[jira] [Work logged] (HADOOP-17511) Add an Audit plugin point for S3A auditing/context

     [ https://issues.apache.org/jira/browse/HADOOP-17511?focusedWorklogId=546110&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-546110 ]

ASF GitHub Bot logged work on HADOOP-17511:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/Feb/21 16:26
            Start Date: 02/Feb/21 16:26
    Worklog Time Spent: 10m 
      Work Description: steveloughran opened a new pull request #2675:
URL: https://github.com/apache/hadoop/pull/2675


   Notion of AuditSpan which is created for a given operation; goal is
   to pass it along everywhere.
   
   It's thread local per FS-instance; store operations pick this up in their
   constructor from the StoreContext.
   
   The entryPoint() method in S3A FS has been enhanced to initiate the spans.
   For this to work, internal code SHALL NOT call those entry points (Done)
   and all public API points MUST be declared as entry points. Tricky given
   the lack of layering in this branch.
   
   The auditing is intended to be a plugin point; currently there is one
   which logs at Info (yes, noisy but good for development)
   
   Change-Id: Idddbbd3138e52b40e97f9c2383453190a02cd8ec
   
   ## NOTICE
   
   Please create an issue in ASF JIRA before opening a pull request,
   and you need to set the title of the pull request which starts with
   the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
   For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 546110)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>          Time Spent: 10m
>  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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org