beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (BEAM-3310) Push metrics to a backend in an runner agnostic way
Date Wed, 21 Mar 2018 14:26:00 GMT

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

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

                Author: ASF GitHub Bot
            Created on: 21/Mar/18 14:25
            Start Date: 21/Mar/18 14:25
    Worklog Time Spent: 10m 
      Work Description: echauchot commented on issue #4548: [BEAM-3310] Metrics pusher
URL: https://github.com/apache/beam/pull/4548#issuecomment-374955081
 
 
   unrelated: build of examples is flaky: sometimes reports error whereas it is success, sometimes
failure in communication:" A work item was attempted 4 times without success. Each time the
worker eventually lost contact with the service. The work item was attempted on: "

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


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

    Worklog Id:     (was: 82764)
    Time Spent: 3h 10m  (was: 3h)

> 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: 3h 10m
>  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)

Mime
View raw message