ASF GitHub Bot commented on CURATOR-349:

Github user cammckenzie commented on the issue:

    Thanks for the PR,
    The content looks OK, but I think that the interface changes need to be 
made backwards compatible. Can we change the OperationTrace to extend the 
existing TimerTrace?
    @Randgalt I'm not really familiar with this code, so it could probably use 
another set of eyes.

> 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

Reply via email to