[
https://issues.apache.org/jira/browse/FLINK-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287702#comment-16287702
]
ASF GitHub Bot commented on FLINK-8080:
---------------------------------------
Github user greghogan commented on a diff in the pull request:
https://github.com/apache/flink/pull/5099#discussion_r156386303
--- Diff: docs/monitoring/metrics.md ---
@@ -333,7 +333,7 @@ reporters will be instantiated on each job and task
manager when they are starte
- `metrics.reporter.<name>.class`: The reporter class to use for the
reporter named `<name>`.
- `metrics.reporter.<name>.interval`: The reporter interval to use for the
reporter named `<name>`.
- `metrics.reporter.<name>.scope.delimiter`: The delimiter to use for the
identifier (default value use `metrics.scope.delimiter`) for the reporter named
`<name>`.
-- `metrics.reporters`: (optional) An include list for reporters to
instantiate. By default all configured reporters will be used.
+- `metrics.reporters`: (optional) A comma-separated include list of
reporters names. By default all configured reporters will be used.
--- End diff --
"reporters" -> "reporter"
> 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)
