[
https://issues.apache.org/jira/browse/CURATOR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605943#comment-15605943
]
ASF GitHub Bot commented on CURATOR-349:
----------------------------------------
Github user lvfangmin commented on the issue:
https://github.com/apache/curator/pull/165
@Randgalt we haven't started the unifying progress yet, since we were
blocked by this feature, it would be better to publicize it on Curator's wiki
when we're actually using it inside FB, I'll let you know, and feel free to
publicize this on Curator's wiki then :)
Unifying the ZooKeeper Java client is our Q4 Goal, and it takes time to
ask/help the internal teams to switch to Curator, so it would be great if we
can have a release at the end of Oct or beginning of Nov. Inside Facebook,
we're still using ZK 3.4, so can we have a release in Curator 2.xxx which
include this change?
> 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)
