[
https://issues.apache.org/jira/browse/BEAM-3310?focusedWorklogId=137469&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-137469
]
ASF GitHub Bot logged work on BEAM-3310:
----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Aug/18 17:20
Start Date: 23/Aug/18 17:20
Worklog Time Spent: 10m
Work Description: StephanEwen commented on issue #4548: [BEAM-3310]
Metrics pusher
URL: https://github.com/apache/beam/pull/4548#issuecomment-415499742
@echauchot Sorry, could you give me a bit of background? The Beam metrics
are mapped to Flink Accumuators, rather than to Flink Metrics. In Flink, the
distinction is:
- Metrics are for monitoring, collecting statistical information, possibly
approximate
- Accumulators are meant to be part of the application logic, side
aggregates, must be exact and are meant to be used by the client program in a
session mode (multiple jobs)
I assume that Beam metrics need to go to Flink Accumulators, rather than
Flink Metrics?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 137469)
Time Spent: 16h (was: 15h 50m)
> Push metrics to a backend in an runner agnostic way
> ---------------------------------------------------
>
> Key: BEAM-3310
> URL: https://issues.apache.org/jira/browse/BEAM-3310
> Project: Beam
> Issue Type: New Feature
> Components: runner-extensions-metrics, sdk-java-core
> Reporter: Etienne Chauchot
> Assignee: Etienne Chauchot
> Priority: Major
> Time Spent: 16h
> Remaining Estimate: 0h
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
