You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/02/13 11:28:11 UTC

[jira] [Commented] (OAK-2516) Add user information in audit events in oak

    [ https://issues.apache.org/jira/browse/OAK-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319833#comment-14319833 ] 

Chetan Mehrotra commented on OAK-2516:
--------------------------------------

Linking to the JR2 issues where audit logger was introduced. Looking at codebase the logger is used in following places

* AbstractBundlePersistenceManager - Logs when a bundle is written and at what size
* ClusterNode - When changes are done in a cluster commit
* BLOBInDataStore - When blob is added to DataStore

> Add user information in audit events in oak
> -------------------------------------------
>
>                 Key: OAK-2516
>                 URL: https://issues.apache.org/jira/browse/OAK-2516
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: oak-jcr
>    Affects Versions: 1.0.11
>            Reporter: Ankush Bangroo
>
> All operations in the repository are being logged by org.apache.jackrabbit.oak.jcr.operations logger, however the above logger does not include the user information triggering these operations.
> Hence we do not have information on the user triggering the read and writes on the repository.



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