[
https://issues.apache.org/jira/browse/CURATOR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15580322#comment-15580322
]
ASF GitHub Bot commented on CURATOR-349:
Github user Randgalt commented on the issue:
https://github.com/apache/curator/pull/165
I think we're almost there. Have you tried merging this with the
CURATOR-3.0 branch yet? Because this is a biggish change it would be good to
have a separate PR based off of CURATOR-3.0 to make sure there are no conflicts
there.
> 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)
