[
https://issues.apache.org/jira/browse/ZEST-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603733#comment-15603733
]
Niclas Hedhman commented on ZEST-190:
-------------------------------------
I agree. The original design was rushed together too quickly and is tied too
much to the CodaHale/Yammer metrics library, instead of doing the "Qi4j Way"
going to the bottom of the actual needs and the unique ways that this platform
can bring this to the users.
> Refine Metrics API/SPI
> ----------------------
>
> Key: ZEST-190
> URL: https://issues.apache.org/jira/browse/ZEST-190
> Project: Zest
> Issue Type: Improvement
> Reporter: Paul Merlin
> Assignee: Paul Merlin
> Fix For: 3.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
(v6.3.4#6332)
