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

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/03 19:26:43 UTC

[GitHub] [beam] kennknowles opened a new issue, #18596: Support MetricsPusher in Dataflow Runner

kennknowles opened a new issue, #18596:
URL: https://github.com/apache/beam/issues/18596

   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._
    
     
   
   Imported from Jira [BEAM-3926](https://issues.apache.org/jira/browse/BEAM-3926). Original Jira may contain additional context.
   Reported by: swegner.
   Subtask of issue #18594


-- 
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.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org