Details
-
New Feature
-
Status: Open
-
P3
-
Resolution: Unresolved
-
None
-
None
Description
The idea is to avoid relying on the runners to provide access to the metrics (either at the end of the pipeline or while it runs) because they don't have all the same capabilities towards metrics (e.g. spark runner configures sinks like csv, graphite or in memory sinks using the spark engine conf). The target is to push the metrics in the common runner code so that no matter the chosen runner, a user can get his metrics out of beam.
Here is the link to the discussion thread on the dev ML: https://lists.apache.org/thread.html/01a80d62f2df6b84bfa41f05e15fda900178f882877c294fed8be91e@%3Cdev.beam.apache.org%3E
And the design doc:
https://s.apache.org/runner_independent_metrics_extraction
Attachments
Issue Links
- supercedes
-
BEAM-2456 Introduce generic metric poll thread interceptor & generic sink
- Resolved
- links to
1.
|
Support MetricsPusher in Dataflow Runner | Open | Unassigned |
|
||||||||
2.
|
Support MetricsPusher in Direct Runner | Open | Unassigned |