[
https://issues.apache.org/jira/browse/CURATOR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605915#comment-15605915
]
ASF GitHub Bot commented on CURATOR-349:
----------------------------------------
Github user lvfangmin commented on the issue:
https://github.com/apache/curator/pull/165
@Randgalt @cammckenzie Thanks for reviewing the code, we're planning to
unify the Zookeeper java client to be Curator inside Facebook, so it's really
important for us to track the client side metrics.
Since we're depending on this patch to unify the java client, may I ask
what's the next scheduled release? And will this patch be in it?
> 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
> Assignee: Jordan Zimmerman
> Fix For: 3.2.1, 2.11.1
>
>
> 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)
