You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gossip.apache.org by "Edward Capriolo (JIRA)" <ji...@apache.org> on 2016/07/20 19:49:20 UTC
[jira] [Updated] (GOSSIP-17) Add metrics to key codepaths
[ https://issues.apache.org/jira/browse/GOSSIP-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated GOSSIP-17:
----------------------------------
Description:
yammer/dropwizzard/codahale metrics would be a good thing to add.
We should use histograms to track how long inter-node operations take.
We should use meters or counters with successful/failed requests.
It would be interesting to keep per host stats but possibly it makes sense to turn that off for larger deployments.
was:
yammer/dropwizzard/codahale metrics would be a good thing to add.
We should use histograms around how long inter-node operations take.
We should use meters or counters with successful/failed requests.
It would be interesting to keep per host stats but possibly it makes sense to turn that off for larger deployments.
> Add metrics to key codepaths
> ----------------------------
>
> Key: GOSSIP-17
> URL: https://issues.apache.org/jira/browse/GOSSIP-17
> Project: Gossip
> Issue Type: New Feature
> Reporter: Edward Capriolo
>
> yammer/dropwizzard/codahale metrics would be a good thing to add.
> We should use histograms to track how long inter-node operations take.
> We should use meters or counters with successful/failed requests.
> It would be interesting to keep per host stats but possibly it makes sense to turn that off for larger deployments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)