[ https://issues.apache.org/jira/browse/STORM-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim resolved STORM-1699. --------------------------------- Resolution: Fixed Fix Version/s: 1.1.0 2.0.0 Marking as 'Resolved' since sub-tasks are resolved. > Improve MetricsConsumer > ----------------------- > > Key: STORM-1699 > URL: https://issues.apache.org/jira/browse/STORM-1699 > Project: Apache Storm > Issue Type: Umbrella > Components: storm-core > Reporter: Jungtaek Lim > Assignee: Jungtaek Lim > Fix For: 2.0.0, 1.1.0 > > > Storm exposes non-stat metrics to users via MetricsConsumer. > Supported feature of metrics is not bad for me. Custom time bucket, exposing > IMetric interface is great. But there seems to some issue with using > MetricsConsumer in some places. > (ex. https://issues.apache.org/jira/browse/AMBARI-13237) > I sought the alternatives, and metrics feature of JStorm seems promising. > Unfortunately it requires breaking backward compatibility completely, and > it's planned to phase 2 we should wait for at least end of phase 1. > For me timeframe for 2.0 seems nondeterministic, and it shouldn't be > backported for keeping compatibility. > Therefore, I'd love to improve current metrics without breaking backward > compatible manner. > While I'm planning to craft the patches around master, it could be applied to > 1.x-branch, and even 0.10.x-branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)