You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2017/08/25 21:49:00 UTC

[jira] [Updated] (KUDU-997) Expose client-side metrics

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

Jean-Daniel Cryans updated KUDU-997:
------------------------------------
    Target Version/s: 1.6.0  (was: 1.5.0)

> Expose client-side metrics
> --------------------------
>
>                 Key: KUDU-997
>                 URL: https://issues.apache.org/jira/browse/KUDU-997
>             Project: Kudu
>          Issue Type: New Feature
>          Components: client
>    Affects Versions: Feature Complete
>            Reporter: Adar Dembo
>         Attachments: patch
>
>
> I think client-side metrics have been a desirable feature for quite some time, but I especially wanted them while debugging KUDU-993.
> There are some challenges in collecting metric data in a cohesive way across the client (at least in C++, where there isn't a completely uniform way to send/receive RPCs). But I think the main challenge is figuring out how to expose it to users. I'm not sure we want to expose metrics.h directly, because it's deeply intertwined with gutil and other Kudu util code.
> I'm attaching a patch I wrote yesterday to help with KUDU-993. It doesn't tackle the API problem at all, but shows how to build a histogram tracking all writes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)