[
https://issues.apache.org/jira/browse/CURATOR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651670#comment-15651670
]
ASF GitHub Bot commented on CURATOR-349:
----------------------------------------
Github user lvfangmin commented on the issue:
https://github.com/apache/curator/pull/172
(Not related with this diff)
@Randgalt , do we have the schedule of Curator release, are we still
blocked by ZOOKEEPER-1525?
The ZOOKEEPER-1525 looks good to me except the new additional parameters
concern, if we can refactor that a bit, I'll add a +1 and ask Ben (one of the
ZooKeeper committer, also my team member) to accelerate the review process and
accept 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)
