Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1595
@harshach @ptgoetz
I believe the best approach is letting users don't care about them.
While I still think we need to renew metrics feature, I also think one of
valid approach for current metrics is spending some more time to provide some
official implementations of metrics consumers which covers popular time-series
DBs like Grafana, and OpenTSDB, InfluxDB, and some others if we have ideas.
This makes us feeling similar to dog-fooding, and will show how good or how
bad is the metrics feature transparently.
(To tell the truth, I realized the limitations of current metrics feature
clearly while playing with Ambari Metric Service Storm sink.)
Contracts will be mostly on our own, so no delegation for the hard thing on
users or dev. of metric consumers.
Just I'm not 100% sure open source metrics consumer projects will reflect
our changed metrics API or contract in time. So while we're improving the
feature, it could unlikely get to the end-users. This is my another concern.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
