[ https://issues.apache.org/jira/browse/ZOOKEEPER-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135623#comment-16135623 ]
ASF GitHub Bot commented on ZOOKEEPER-1260: ------------------------------------------- GitHub user arshadmohammad opened a pull request: https://github.com/apache/zookeeper/pull/338 ZOOKEEPER-1260:Audit logging in ZooKeeper servers. Audit logging in ZooKeeper Servers. You can merge this pull request into a Git repository by running: $ git pull https://github.com/arshadmohammad/zookeeper ZOOKEEPER-1260-AuditLog Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/338.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #338 ---- commit 502fbf7b2127cc4cf8284d8ecc181ae47e02b2d6 Author: Mohammad Arshad <ars...@apache.org> Date: 2017-07-11T14:42:13Z ZOOKEEPER-1260:Audit logging in ZooKeeper Servers. ---- > Audit logging in ZooKeeper servers. > ----------------------------------- > > Key: ZOOKEEPER-1260 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1260 > Project: ZooKeeper > Issue Type: New Feature > Reporter: Mahadev konar > Assignee: Mohammad Arshad > Fix For: 3.5.4, 3.6.0 > > Attachments: ZOOKEEPER-1260-01.patch, zookeeperAuditLogs.pdf > > > Lots of users have had questions on debugging which client changed what znode > and what updates went through a znode. We should add audit logging as in > Hadoop (look at Namenode Audit logging) to log which client changed what in > the zookeeper servers. This could just be a log4j audit logger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)