atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Kantor (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (ATLAS-1391) Add exclusion mechanism for Atlas audit mechanism
Date Thu, 05 Jan 2017 19:20:58 GMT

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

David Kantor reopened ATLAS-1391:
---------------------------------

Reopening based on email from [~madhan.neethiraj] regarding defect raised by Coverity scan.

{noformat}Please find the latest report on new defect(s) introduced to Apache Atlas found
with Coverity Scan.
    
    1 new defect(s) introduced to Apache Atlas found with Coverity Scan.
    
    
    New defect(s) Reported-by: Coverity Scan
    Showing 1 of 1 defect(s)
    
    
    ** CID 155185:  Null pointer dereferences  (FORWARD_NULL)
    /repository/src/main/java/org/apache/atlas/util/AtlasRepositoryConfiguration.java: 116
in org.apache.atlas.util.AtlasRepositoryConfiguration.getAuditExcludedOperations(org.apache.commons.configuration.Configuration)()
    
    
    ________________________________________________________________________________________________________
    *** CID 155185:  Null pointer dereferences  (FORWARD_NULL)
    /repository/src/main/java/org/apache/atlas/util/AtlasRepositoryConfiguration.java: 116
in org.apache.atlas.util.AtlasRepositoryConfiguration.getAuditExcludedOperations(org.apache.commons.configuration.Configuration)()
    110                 } catch (AtlasException e) {
    111                     LOG.error(" Error reading operations for auditing ", e);
    112                 }
    113             }
    114             if (skippedOperations == null) {
    115                 skippedOperations = new ArrayList<String>();
    >>>     CID 155185:  Null pointer dereferences  (FORWARD_NULL)
    >>>     Calling a method on null object "config".
    116                     String[] skipAuditForOperations = config
    117                             .getStringArray(AUDIT_EXCLUDED_OPERATIONS);
    118                     if (skipAuditForOperations != null
    119                             && skipAuditForOperations.length > 0) {
    120                         for (String skippedOperation : skipAuditForOperations) {
    121                             String[] excludedOperations = skippedOperation.trim().toLowerCase().split(SEPARATOR);
{noformat}

> 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
>
>
> 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)

Mime
View raw message