You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Fangmin Lv (JIRA)" <ji...@apache.org> on 2016/09/15 08:42:20 UTC

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

     [ https://issues.apache.org/jira/browse/CURATOR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fangmin Lv updated CURATOR-349:
-------------------------------
    Summary: Expose extra metrics in TracerDriver  (was: Expose extra metrics in TracerDeriver)

> Expose extra metrics in TracerDriver
> ------------------------------------
>
>                 Key: CURATOR-349
>                 URL: https://issues.apache.org/jira/browse/CURATOR-349
>             Project: Apache Curator
>          Issue Type: New Feature
>          Components: Recipes
>            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)