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

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

                Author: ASF GitHub Bot
            Created on: 13/Apr/18 13:32
            Start Date: 13/Apr/18 13:32
    Worklog Time Spent: 10m 
      Work Description: echauchot commented on issue #4548: [BEAM-3310] Metrics 
pusher
URL: https://github.com/apache/beam/pull/4548#issuecomment-381134930
 
 
   @lukecwik @swegner : I finalized a test that I wanted to do: run the metrics 
pusher in a real cluster (I chose spark). It works fine. Can we move forward 
and merge this PR as it is and consider it as **the default implementation that 
java sdks and java runners are free to use** (like the philosophy of 
runner-core-java module)?  
   We can address non java sdk/runners separately in the tickets 
https://issues.apache.org/jira/browse/BEAM-3967 and 
https://issues.apache.org/jira/browse/BEAM-3926.
   @swegner you gave LGTM, so I think we can merge.

----------------------------------------------------------------
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:
us...@infra.apache.org


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

    Worklog Id:     (was: 90811)
    Time Spent: 4h  (was: 3h 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: sdk-java-core
>            Reporter: Etienne Chauchot
>            Assignee: Etienne Chauchot
>            Priority: Major
>          Time Spent: 4h
>  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)

Reply via email to