polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niclas Hedhman (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (POLYGENE-190) Refine Metrics API/SPI
Date Sat, 28 Apr 2018 07:57:00 GMT

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

Niclas Hedhman closed POLYGENE-190.

> Refine Metrics API/SPI
> ----------------------
>                 Key: POLYGENE-190
>                 URL: https://issues.apache.org/jira/browse/POLYGENE-190
>             Project: Polygene
>          Issue Type: Improvement
>            Reporter: Paul Merlin
>            Assignee: Paul Merlin
>            Priority: Major
>             Fix For: 3.0.0
> The current metrics API mixes in pure metrics aspects with reporting ones. The factories
should not require the reporting duration unit nor the rate unit nor display names. These
should be chosen when using reporters, whatever the metrics collection backend.
> Let's use {{Stream<Metric>}} instead of {{Iterable}} in {{MetricsFactory::registered()}}.
> {{@TimingCapture}} concern should name timers with some "Structure path" by default,
like we do in jmx support, and allow to name the underlying timer with an annotation parameter.

This message was sent by Atlassian JIRA

View raw message