[ 
https://issues.apache.org/jira/browse/ATLAS-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neeru Gupta updated ATLAS-1391:
-------------------------------
     Attachment: rb55227.patch
    Description: 
As a consumer of Atlas, I want to be able to exclude certain operations, such 
as ping, from the audit log so that it does not get filled up with noise.

This should be a general mechanism. It should be possible to configure the 
endpoints being excluded in the Atlas configuration file. The only requirement 
at this time is to be able to filter based on the high level operation being 
invoked (ie ping, version, etc). There is no need to be able to filter based on 
the arguments to the operation.


  was:

As a consumer of Atlas, I want to be able to exclude certain operations, such 
as ping, from the audit log so that it does not get filled up with noise.

This should be a general mechanism. It should be possible to configure the 
endpoints being excluded in the Atlas configuration file. The only requirement 
at this time is to be able to filter based on the high level operation being 
invoked (ie ping, version, etc). There is no need to be able to filter based on 
the arguments to the operation.



> Add exclusion mechanism for Atlas audit mechanism
> -------------------------------------------------
>
>                 Key: ATLAS-1391
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1391
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Neeru Gupta
>            Assignee: Neeru Gupta
>             Fix For: 0.8-incubating
>
>         Attachments: rb54907(1).patch, rb55227.patch
>
>
> As a consumer of Atlas, I want to be able to exclude certain operations, such 
> as ping, from the audit log so that it does not get filled up with noise.
> This should be a general mechanism. It should be possible to configure the 
> endpoints being excluded in the Atlas configuration file. The only 
> requirement at this time is to be able to filter based on the high level 
> operation being invoked (ie ping, version, etc). There is no need to be able 
> to filter based on the arguments to the operation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to