Github user zentol commented on a diff in the pull request:
https://github.com/apache/flink/pull/2285#discussion_r71881022
--- Diff: docs/apis/metrics.md ---
@@ -227,14 +227,25 @@ or by assigning unique names to jobs and operators.
## Reporter
-Metrics can be exposed to an external system by configuring a reporter in
`conf/flink-conf.yaml`.
-
-- `metrics.reporter.class`: The class of the reporter to use.
- - Example: org.apache.flink.metrics.reporter.JMXReporter
-- `metrics.reporter.arguments`: A list of named parameters that are passed
to the reporter.
- - Example: --host localhost --port 9010
-- `metrics.reporter.interval`: The interval between reports.
- - Example: 10 SECONDS
+Metrics can be exposed to an external system by configuring a one or
several reporters in `conf/flink-conf.yaml`.
+
+- `metrics.reporters`: The list of named reporters, i.e. "foo,bar".
+- `metrics.reporter.<name>.<config>`: Generic setting `<config>` for the
reporter named `<name>`.
+- `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>`.
+
+All reporters must at least have the `class` config, some allow specifying
a reporting `interval`. Bellow,
+we will list more settings specific to each reporter.
+
+Example reporter configuration for using the built-in JMX reporter:
+
+```
+metrics.reporters: my_jmx_reporter
--- End diff --
i think we should show the configuration for multiple reporters
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
