You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Brian Brazil (JIRA)" <ji...@apache.org> on 2015/12/01 11:45:10 UTC

[jira] [Commented] (ZOOKEEPER-2093) Expose cumulative latency and request count

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

Brian Brazil commented on ZOOKEEPER-2093:
-----------------------------------------

Hi, it's been a year. Is this likely to ever get merged?

> Expose cumulative latency and request count
> -------------------------------------------
>
>                 Key: ZOOKEEPER-2093
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2093
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: jmx, server
>            Reporter: Brian Brazil
>            Priority: Minor
>              Labels: patch
>             Fix For: 3.6.0
>
>         Attachments: export-cumulative-latency.patch
>
>
> Currently Zookeeper exposes min, max and average since server start request latency.
> It'd also be useful to be able to calculate latency over a given time period. This patch exposes the total latency, and count of number of request. By tracking how these values increase over time, your monitoring system can calculate the average latency over a given period of time.
> This only provides milliseconds, as that's what's currently there.
> I'm seeing a test failure on ClientPortBindTest.testBindByAddress, this appears to be due to my IPv6 setup.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)