[
https://issues.apache.org/jira/browse/ZOOKEEPER-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419835#comment-15419835
]
Arshad Mohammad commented on ZOOKEEPER-1260:
--------------------------------------------
[~eribeiro] , regarding your comments on ZOOKEEPER-2287.
First of all, Thanks for sharing your thoughts. But I have completely different
opinion on this..
# JMX matrices and audit logs serve completely different purposes. Zookeeper
JMX metrics give the current state of the system.
Where as the audit log, in general, give the history of the operations that
change the system state. So adding more matrices can not replace audit log
# Audit logs does not log all the operations, they log only the operations
which change the state of the system. So the amount of audit log compared to
general log is very very less.
# When the audit log is disabled, the performance impact is negligible. But
when audit log is enabled offcourse there will be slight performace
degradation, but that is optional to user whether they want the audit log or
slightly better performance
> Audit logging in ZooKeeper servers.
> -----------------------------------
>
> Key: ZOOKEEPER-1260
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1260
> Project: ZooKeeper
> Issue Type: New Feature
> Affects Versions: 3.4.0
> Reporter: Mahadev konar
> Assignee: Arshad Mohammad
> Fix For: 3.6.0
>
>
> 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.3.4#6332)
