[jira] [Resolved] (STORM-3670) Separate configurations for daemon metric reporters and topology metrics reporters

["Ethan Li (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STORM-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Li resolved STORM-3670.
-----------------------------
    Fix Version/s: 2.3.0
       Resolution: Fixed

Merged to master (bb3e7a195a1a97f4184a48bb4ad07a398194ed1a)

> Separate configurations for daemon metric reporters and topology metrics reporters
> ----------------------------------------------------------------------------------
>
>                 Key: STORM-3670
>                 URL: https://issues.apache.org/jira/browse/STORM-3670
>             Project: Apache Storm
>          Issue Type: Improvement
>            Reporter: Ethan Li
>            Assignee: Ethan Li
>            Priority: Major
>             Fix For: 2.3.0
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> 1. storm.metrics.reporters should be configurable per topology.
> Currently, storm.metrics.reporters config is retrieved from storm daemon config (more precisely, supervisor config) so it can't be configured at topology level. User should be able to choose their own reporter for their topology
> 2. storm.metrics.reporters is actually only used in workers. So we should remove unnecessary "daemons" section in the reporter conf to make it clear
> 3. configs like storm.daemon.metrics.reporter.plugin.rate.unit should only be used by daemon metric reporters (storm.daemon.metrics.reporter.plugins)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)