Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2226
I tried to see if we can move the entire set of metrics classes to the
independent `flink-metrics-core` module. Here is how that would look like:
https://github.com/StephanEwen/incubator-flink/tree/move_metrics
- The runtime-specific metric groups are in `runtime.metrics` in
`flink-runtime`. It makes sense dependency wise, because that way, we can
actually use the proper types (like `ExecutionID`)
- ScopeFormats are also bound to the component metric groups, not the
registry as a whole
- Everything else is in the `flink-metrics-core` module.
Remaining issues:
- The JMX reporter currently uses the `NetUtils`, which are now not
available any more.
- The `MetricRegistry` relied on `Configuration` before. It can now only
rely on `MetricConfig`, which we have to efficiently extract from the
configuration.
---
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.
---
