[ https://issues.apache.org/jira/browse/STORM-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim resolved STORM-1700. --------------------------------- Resolution: Fixed Fix Version/s: 1.1.0 2.0.0 Merged into master and 1.x-branch. > Introduce 'whitelist' / 'blacklist' option to MetricsConsumer > ------------------------------------------------------------- > > Key: STORM-1700 > URL: https://issues.apache.org/jira/browse/STORM-1700 > Project: Apache Storm > Issue Type: Sub-task > Components: storm-core > Affects Versions: 1.0.0, 2.0.0 > Reporter: Jungtaek Lim > Assignee: Jungtaek Lim > Fix For: 2.0.0, 1.1.0 > > > Storm provides various metrics by default, and so on some external modules > (storm-kafka). > When we register MetricsConsumer, MetricsConsumer should handle all of > metrics. If MetricsConsumer cannot keep up with these metrics, only way to > keep up is increasing parallelism, which seems limited. Furthermore, some > users don't want to care about some metrics since unintended metrics will > fill external storage. > Though MetricsConsumer itself can filter metrics by name, it would be better > to support filter by Storm side. It will reduce the redundant works for Storm > community. > If we provide filter options, it would be great. -- This message was sent by Atlassian JIRA (v6.3.4#6332)