You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Etienne Chauchot (Jira)" <ji...@apache.org> on 2022/01/12 13:05:00 UTC

[jira] [Commented] (BEAM-3926) Support MetricsPusher in Dataflow Runner

    [ https://issues.apache.org/jira/browse/BEAM-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474507#comment-17474507 ] 

Etienne Chauchot commented on BEAM-3926:
----------------------------------------

[~kenn] still no metricsPusher support in DataFlow runner

> Support MetricsPusher in Dataflow Runner
> ----------------------------------------
>
>                 Key: BEAM-3926
>                 URL: https://issues.apache.org/jira/browse/BEAM-3926
>             Project: Beam
>          Issue Type: Sub-task
>          Components: runner-dataflow
>            Reporter: Scott Wegner
>            Priority: P3
>          Time Spent: 5h 50m
>  Remaining Estimate: 0h
>
> See [relevant email thread|https://lists.apache.org/thread.html/2e87f0adcdf8d42317765f298e3e6fdba72917a72d4a12e71e67e4b5@%3Cdev.beam.apache.org%3E]. From [~echauchot]:
>   
> _AFAIK Dataflow being a cloud hosted engine, the related runner is very different from the others. It just submits a job to the cloud hosted engine. So, no access to metrics container etc... from the runner. So I think that the MetricsPusher (component responsible for merging metrics and pushing them to a sink backend) must not be instanciated in DataflowRunner otherwise it would be more a client (driver) piece of code and we will lose all the interest of being close to the execution engine (among other things instrumentation of the execution of the pipelines).  I think that the MetricsPusher needs to be instanciated in the actual Dataflow engine._
>  
>   



--
This message was sent by Atlassian Jira
(v8.20.1#820001)