curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CURATOR-349) Expose extra metrics in TracerDriver
Date Wed, 21 Sep 2016 01:41:20 GMT


ASF GitHub Bot commented on CURATOR-349:

GitHub user lvfangmin opened a pull request:

    [CURATOR-349] Expose extra metrics in TracerDriver


You can merge this pull request into a Git repository by running:

    $ git pull CURATOR-349

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #165
commit 48c687c241e4b95b4384c91609cc7b4a5dd68ae6
Author: allenlyu <>
Date:   2016-09-20T21:56:47Z

    [CURATOR-349] Expose extra metrics in TracerDriver


> Expose extra metrics in TracerDriver
> ------------------------------------
>                 Key: CURATOR-349
>                 URL:
>             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,

This message was sent by Atlassian JIRA

View raw message