You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@storm.apache.org by "Ethan Li (Jira)" <ji...@apache.org> on 2020/07/08 19:00:00 UTC

[jira] [Updated] (STORM-3670) storm.metrics.reporters should be used as a topology level config

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

Ethan Li updated STORM-3670:
----------------------------
    Description: 
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.



  was:
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.

Note: For daemons, we already have "storm.daemon.metrics.reporter.plugins" for the purpose of configuring reporters for daemons.


> storm.metrics.reporters should be used as a topology level config
> -----------------------------------------------------------------
>
>                 Key: STORM-3670
>                 URL: https://issues.apache.org/jira/browse/STORM-3670
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Ethan Li
>            Assignee: Ethan Li
>            Priority: Major
>
> 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.



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