You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/18 17:07:30 UTC
[jira] [Commented] (BEAM-1344) Uniform metrics step name semantics
[ https://issues.apache.org/jira/browse/BEAM-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179924#comment-17179924 ]
Beam JIRA Bot commented on BEAM-1344:
-------------------------------------
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.
> Uniform metrics step name semantics
> -----------------------------------
>
> Key: BEAM-1344
> URL: https://issues.apache.org/jira/browse/BEAM-1344
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Aviem Zur
> Priority: P2
> Labels: stale-P2
>
> Agree on and implement uniform metrics step name semantics which runners would adhere to.
> Current discussion seems to point at a string with the pipeline graph path to the step's transform. Something along the lines of: "PBegin/SomeInputTransform/SomeParDo/...MyTransform.#Running_number_for_collisions".
> Also agree on and implement metrics querying semantics. Current discussion seems to point at a substring or regex matching of steps on given string input.
> [Original dev list discussion|https://lists.apache.org/thread.html/476bf8f8b1bd63ec49a9f4f45d87402d49b9c887216f3b54cb748a12@%3Cdev.beam.apache.org%3E]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)