[ https://issues.apache.org/jira/browse/CURATOR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507932#comment-15507932 ]
ASF GitHub Bot commented on CURATOR-349: ---------------------------------------- GitHub user lvfangmin opened a pull request: https://github.com/apache/curator/pull/164 [CURATOR-349] Expose extra metrics in TracerDriver You can merge this pull request into a Git repository by running: $ git pull https://github.com/lvfangmin/curator CURATOR-349 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/curator/pull/164.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 #164 ---- commit c3e2f24525cc722642b108e4da95ef3f73373d2c Author: allenlyu <allen...@fb.com> Date: 2016-09-20T21:56:47Z [CURATOR-349] Expose extra metrics in TracerDriver ---- > Expose extra metrics in TracerDriver > ------------------------------------ > > Key: CURATOR-349 > URL: https://issues.apache.org/jira/browse/CURATOR-349 > Project: Apache Curator > Issue Type: Improvement > Components: Framework > Reporter: Fangmin Lv > > Currently, the TracerDriver exposed the latency of ZK operations, in > multi-tenant environment, extra metrics are required to help tracing and > monitoring: > * the bytes being sent and received, so we can monitor the client usage > scenarios. > * which ensemble participant the client is talking to, used to find out the > problematic Zk server when the issue happened. > * the z-node path, to easily find out which z-node caused the problem, like > high load, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)