Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
Date: Wed, 28 Sep 2016 10:29:20 +0000 (UTC)
From: "Jordan Zimmerman (JIRA)" <jira@apache.org>
To: dev@curator.apache.org
Message-ID: <JIRA.13005109.1473928336000.685637.1475058560656@Atlassian.JIRA>
In-Reply-To: <JIRA.13005109.1473928336000@Atlassian.JIRA>
References: <JIRA.13005109.1473928336000@Atlassian.JIRA> <JIRA.13005109.1473928336954@arcas>
Subject: [jira] [Assigned] (CURATOR-349) Expose extra metrics in
 TracerDriver
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 28 Sep 2016 10:29:22 -0000


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

Jordan Zimmerman reassigned CURATOR-349:
----------------------------------------

    Assignee: Jordan Zimmerman

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