curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-349) Expose extra metrics in TracerDriver
Date Thu, 22 Sep 2016 16:00:23 GMT

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

ASF GitHub Bot commented on CURATOR-349:
----------------------------------------

Github user lvfangmin commented on the issue:

    https://github.com/apache/curator/pull/165
  
    Thanks @cammckenzie for review, the TimerTrace is actually an internal helper class, it
shouldn't have any backwards compatible problem. It is the TracerDriver that may have backwards
compatible issue, but more strictly it's not a backwards compatible issue, it's that the users
who are using TracerDriver have to change their implementation based on the new interface.
    
    @Randgalt can you help review on it, it's a feature required internally and we want to
have it as soon as possible, thanks :)


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

Mime
View raw message