> If I understand correctly, a slow operation log with the threshold for
> logging set to 0 should accomplish what you are trying to accomplish.
Yes, that would work.
You may also want to consider taking a look and reviewing the change
> proposed here:
You may also want to consider taking a look and reviewing the change proposed
here: https://github.com/apache/zookeeper/pull/307
If I understand correctly, a slow operation log with the threshold for logging
set to 0 should accomplish what you are trying to accomplish.
Thanks,
Abe
On Wed, Mar
Cool, monitoring the transaction makes much sense I think.
Interesting to see this tool, I didn't know about it yet. For some reason
it replicates most of the logic in FileSnap and FileTxnLog classes, but at
the same time it uses ZooKeeper as a dependency.
Regards,
Andor
On Wed, Mar 7, 2018
As you mentioned, enabling trace/debug might impact performance.
Here's the approach I'm using now.
-
Parse the Zookeeper transaction logs. The best repo I've found to do
this is https://github.com/alenca/zklogtool. It's feature packed. The
only downside is that it won't record the
Hi Zod,
Have you checked TRACE logging of client requests? (
http://zookeeper.apache.org/doc/r3.4.11/zookeeperAdmin.html#sc_authOptions)
Not sure how much different is from what you refer as 'debug logs', but it
might worth a try. It generates log messages like:
TRACE
Unfortunately, parsing debug log is no-go since it doesn't print the
complete command.
I've 2 approached in mind as of now
1. Modify of org.apache.zookeeper.server.LogFormatter to support "tailing".
2. Use ngrep on my local to monitor the network traffic to remote ZK host &
port 2181
Will get
Hi Zod,
I think there's no such thing in ZooKeeper currently other than debug logs.
You might want to attach some processing engine to the debug log feed and
parse and output data which is important for you into MySQL or Redis
database.
The downside of this approach is debug logging has
