[ 
https://issues.apache.org/jira/browse/BEAM-7605?focusedWorklogId=305260&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305260
 ]

ASF GitHub Bot logged work on BEAM-7605:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/Sep/19 15:50
            Start Date: 02/Sep/19 15:50
    Worklog Time Spent: 10m 
      Work Description: steveniemitz commented on pull request #8913: 
[BEAM-7605] Allow user-code to read counters from the dataflow worker
URL: https://github.com/apache/beam/pull/8913
 
 
   
 
----------------------------------------------------------------
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:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 305260)
    Time Spent: 3h  (was: 2h 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: 3h
>  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
(v8.3.2#803003)

Reply via email to