[jira] [Commented] (CURATOR-349) Expose extra metrics in TracerDriver

["Fangmin Lv (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CURATOR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15492784#comment-15492784 ] 

Fangmin Lv commented on CURATOR-349:
------------------------------------

To add this support, the TracerDriver interface need to be changed, if we want to make it backward compatible, maybe a new interface such as AdvancedTracerDriver is a better idea. But I'm doubt this is a real issue we need to consider. Any idea?

> 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)