[
https://issues.apache.org/jira/browse/BEAM-7605?focusedWorklogId=263979&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-263979
]
ASF GitHub Bot logged work on BEAM-7605:
----------------------------------------
Author: ASF GitHub Bot
Created on: 20/Jun/19 18:09
Start Date: 20/Jun/19 18:09
Worklog Time Spent: 10m
Work Description: steveniemitz commented on issue #8913: [BEAM-7605]
Allow user-code to read counters from the dataflow worker
URL: https://github.com/apache/beam/pull/8913#issuecomment-504127086
looking through MetricsPusher a little more, is the intent that it runs on
the "submitter" or the workers themselves? From what I can tell with the flink
and spark impls, it _looks_ like they run on the submitter and poll the running
job.
The "publish from submitter" case doesn't work very well for my use-case,
because I want both non-aggregated metrics, and also don't want the submitter
to have to run forever while the job runs.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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: 263979)
Time Spent: 1h (was: 50m)
> Provide a way for user code to read dataflow runner stats
> ---------------------------------------------------------
>
> Key: BEAM-7605
> URL: https://issues.apache.org/jira/browse/BEAM-7605
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: Steve Niemitz
> Assignee: Steve Niemitz
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The dataflow runner collects (and publishes to the dataflow service) a large
> number of useful stats. While these can be polled from the dataflow service
> via its API, there are a few downsides to this:
> * it requires another process to poll and collect the stats
> * the stats are aggregated across all workers, so per-worker stats are lost
> It would be simple to provide a hook to allow users to receive stats updates
> as well, and then do whatever they want with them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
