[
https://issues.apache.org/jira/browse/STORM-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Govind Menon updated STORM-3502:
--------------------------------
Affects Version/s: (was: 2.2.0)
2.3.0
> metrics-core isn't shaded
> -------------------------
>
> Key: STORM-3502
> URL: https://issues.apache.org/jira/browse/STORM-3502
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-client, storm-server, storm-webapp
> Affects Versions: 2.3.0
> Reporter: Diogo Soares
> Priority: Minor
>
> "Apache Storm version 1.2 introduced a new metrics system for reporting
> internal statistics (e.g. acked, failed, emitted, transferred, disruptor
> queue metrics, etc.) as well as a new API for user defined metrics.
> The new metrics system is based on [Dropwizard
> Metrics|http://metrics.dropwizard.io/].";
> Currently at my company we're still using a storm version that does not have
> any metric reporter (1.1.x), we're planning to move to 2.2 version, however
> since, we've been using codahale metrics reporter to track some events on
> storm and since the newer versions already include this, it means that we
> have to change every topology we already have in production.
> It would be nice, that this dependency inside of storm could be shaded in
> order to ease any migration, or at least without a lot of refactoring on the
> topologies, I assume this problem must be similar in other companies, and
> storm already does this for other artifacts.
> I would be happy to perform the necessary changes in order to accomplish this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
