[
https://issues.apache.org/jira/browse/ZOOKEEPER-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182183#comment-13182183
]
kishore gopalakrishna commented on ZOOKEEPER-1183:
--------------------------------------------------
Hi Camille,
Yes, I wanted to enhance it as well. I was actually planning enhance it to a
audit log and have a tool called zk data tree timeline.
Requirements were
* For a given path show the create, modify, delete sequence for a given range
of time.
* Given a session tell when was it created, who created it (unfortunately i
cant get ip from transaction log), when was it closed.
There were few more things I wanted but dont remember now.
The Zk time line tool i had in mind was a applet with a time slider. It show
the zk data tree. One should be able to use the slider to move back and forth
in time and see the tree. This is very useful in debugging issues.
I have written a tool(not ui) for my own project which parses the ZK
transaction log and actually gives us the ability to know sequence of events
that happened in the application. Unfortunately this is very specific to my
application and others may not be able to use this.
Let me know what you about a tool like this. If there is enough interest, I can
spend time making it generic enough for others to use.
> Enhance LogFormatter to output additional detail from transaction log
> ---------------------------------------------------------------------
>
> Key: ZOOKEEPER-1183
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1183
> Project: ZooKeeper
> Issue Type: Improvement
> Affects Versions: 3.4.0
> Reporter: kishore gopalakrishna
> Assignee: kishore gopalakrishna
> Priority: Minor
> Attachments: ZOOKEEPER-1183.patch
>
>
> Current LogFormatter prints the following information
> ZooKeeper Transactional Log File with dbid 0 txnlog format version 2
> 8/15/11 1:55:36 PM PDT session 0x131cf1a236f0014 cxid 0x0 zxid 0xf01
> createSession
> 8/15/11 1:55:57 PM PDT session 0x131cf1a236f0000 cxid 0x55f zxid 0xf02 setData
> 8/15/11 1:56:00 PM PDT session 0x131cf1a236f0015 cxid 0x0 zxid 0xf03
> createSession
> ...
> ..
> 8/15/11 2:00:33 PM PDT session 0x131cf1a236f001c cxid 0x36 zxid 0xf6b setData
> 8/15/11 2:00:33 PM PDT session 0x131cf1a236f0021 cxid 0xa1 zxid 0xf6c create
> 8/15/11 2:00:33 PM PDT session 0x131cf1a236f001b cxid 0x3e zxid 0xf6d setData
> 8/15/11 2:00:33 PM PDT session 0x131cf1a236f001e cxid 0x3e zxid 0xf6e setData
> 8/15/11 2:00:33 PM PDT session 0x131cf1a236f001d cxid 0x41 zxid 0xf6f setData
> Though this is good information, it does not provide additional information
> like
> createSession: which ip created the session and its time out
> set|get|delete: the path and data
> create: path created and createmode along with data
> We can add additional parameter -detail and provide detailed output of the
> transaction.
> Outputting data is slightly tricky since we cant print data without
> understanding the format. We need not print this for now.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
