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

Chesnay Schepler updated FLINK-8080:
------------------------------------
    Description: 
Currently, in order to use a reporter one must configure something like this:
{code}
metrics.reporters: jmx
metrics.reporter.jmx.class: ...
{code}

It would be neat if users did not have to set {{metrics.reporters}}. We can 
accomplish this by a scanning the configuration for configuration keys starting 
with {{metrics.reporter.}} and using the next word as a reporter name.

We can instead use this key as an include list for reporters that should be 
started, which should preserve existing behavior.

  was:
Currently, in order to use a reporter one must configure something like this:
{code}
metrics.reporters: jmx
metrics.reporter.jmx.class: ...
{code}

It would be neat if users did not have to set {{metrics.reporters}}. We can 
accomplish this by a scanning the configuration for configuration keys starting 
with {{metrics.reporter.}} and using the next word as a reporter name.


> Rework "metrics.reporters" config option to an optional include list
> --------------------------------------------------------------------
>
>                 Key: FLINK-8080
>                 URL: https://issues.apache.org/jira/browse/FLINK-8080
>             Project: Flink
>          Issue Type: Improvement
>          Components: Configuration, Metrics
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Trivial
>             Fix For: 1.5.0
>
>
> Currently, in order to use a reporter one must configure something like this:
> {code}
> metrics.reporters: jmx
> metrics.reporter.jmx.class: ...
> {code}
> It would be neat if users did not have to set {{metrics.reporters}}. We can 
> accomplish this by a scanning the configuration for configuration keys 
> starting with {{metrics.reporter.}} and using the next word as a reporter 
> name.
> We can instead use this key as an include list for reporters that should be 
> started, which should preserve existing behavior.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to