sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Ma (JIRA)" <>
Subject [jira] [Commented] (SENTRY-179) Generate audit trail for Sentry DBStore service actions
Date Wed, 16 Jul 2014 03:16:05 GMT


Colin Ma commented on SENTRY-179:

hi Prasad, For the log4j we can define the appender with the specific name which is defined
in the class, for example:
      in class SentryPolicyStoreProcessor, we will create the instance for Logger like:
             // specific name: org.apache.sentry.provider.db.service.thrift.SentryPolicyStoreProcessor
            private static final Logger sentryLog1 = LoggerFactory.getLogger(SentryPolicyStoreProcessor.class);
            // specific name: logger2
            private static final Logger sentryLog2 = LoggerFactory.getLogger("logger2");

      in file, we can do the configuration like:
             log4j.logger.logger2=INFO, sentry2

According to the above configuration, all logs generated by  sentryLog1 will be output to
/var/log/sentry/sentry1.log and sentry2.log will include the logs generated by sentryLog2.
This won't conflict with the normal log4j message.

> Generate audit trail for Sentry DBStore service actions
> -------------------------------------------------------
>                 Key: SENTRY-179
>                 URL:
>             Project: Sentry
>          Issue Type: Improvement
>    Affects Versions: 1.4.0
>            Reporter: Prasad Mujumdar
>            Assignee: Colin Ma
>         Attachments: Design Document of Supporting Audit Log.pdf
> The Sentry DB store should generate audit logs for authorization metadata change requests.

This message was sent by Atlassian JIRA

View raw message