[ https://issues.apache.org/jira/browse/ZOOKEEPER-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137165#comment-16137165 ]
ASF GitHub Bot commented on ZOOKEEPER-1260: ------------------------------------------- Github user arshadmohammad commented on a diff in the pull request: https://github.com/apache/zookeeper/pull/338#discussion_r134566167 --- Diff: src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml --- @@ -931,7 +931,19 @@ server.3=zoo3:2888:3888</programlisting> feature. Default is "true"</para> </listitem> </varlistentry> - + <varlistentry> + <term>audit.enabled</term> + <listitem> + <para>(Java system property: + <emphasis role="bold">zookeeper.audit.enabled</emphasis>) + </para> + <para> + <emphasis role="bold">New in 3.5.3:</emphasis> --- End diff -- corrected it > Audit logging in ZooKeeper servers. > ----------------------------------- > > Key: ZOOKEEPER-1260 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1260 > Project: ZooKeeper > Issue Type: New Feature > Components: server > 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)