[jira] [Commented] (BEAM-2602) Fully support dropwizard metrics in beam and runners

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

Beam JIRA Bot commented on BEAM-2602:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Fully support dropwizard metrics in beam and runners
> ----------------------------------------------------
>
>                 Key: BEAM-2602
>                 URL: https://issues.apache.org/jira/browse/BEAM-2602
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-core, runner-flink, runner-spark, sdk-java-core
>    Affects Versions: Not applicable
>            Reporter: Cody
>            Priority: P2
>              Labels: stale-P2, triaged
>
> As proposed at https://docs.google.com/document/d/1-35iyCIJ9P4EQONlakgXBFRGUYoOLanq2Uf2sw5EjJw/edit?usp=sharing , I'd like to add full support of dropwizard metrics by delegating beam metrics to runners.
> The proposal involves a few subtasks, as far as I see, including:
> 1. add Meter interface in sdk-java-core and extend Distribution to support quantiles
> 2. add MeterData, extend DistributionData. Merge {Counter/Meter/Gauge/Distribution}Data instead of Counter/Meter/Gauge/Distribution at accumulators.
> 3. Runner changes over improved metrics. 
> I will create subtasks later if there's no objection.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)