[
https://issues.apache.org/jira/browse/CURATOR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605919#comment-15605919
]
ASF GitHub Bot commented on CURATOR-349:
----------------------------------------
Github user Randgalt commented on the issue:
https://github.com/apache/curator/pull/165
@lvfangmin
> we're planning to unify the Zookeeper java client to be Curator inside
Facebook
Wow - cool! Can I publicize that on Curator's wiki?
> may I ask what's the next scheduled release? And will this patch be in it?
Personally, I'm waiting on ZOOKEEPER-2169 and ZOOKEEPER-1525 and was
planning on doing a build when those are ready. Supposedly it will be in ZK
3.6. How long can you wait?
> 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)
