[jira] [Commented] (BEAM-9997) Improve step names in portable runners

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

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

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

This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.

> Improve step names in portable runners
> --------------------------------------
>
>                 Key: BEAM-9997
>                 URL: https://issues.apache.org/jira/browse/BEAM-9997
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-spark
>            Reporter: Kyle Weaver
>            Priority: P3
>              Labels: portability-spark
>
> Step names are currently inconsistent between runners. This is probably unavoidable due to fusion, but we should design a system that is more consistent between runners so that most metric queries against the Fn API runner can also be used with the portable Flink and Spark runners.
> Spark Runner:
> MetricKey(step=ref_AppliedPTransform_count1_17, metric=MetricName(namespace=ns, name=counter), labels={}): 2
> MetricKey(step=ref_AppliedPTransform_count2_18, metric=MetricName(namespace=ns, name=counter), labels={}): 4
> ...
> Fn API Runner:
> MetricKey(step=count1, metric=MetricName(namespace=ns, name=counter), labels={}): 2,
> MetricKey(step=count2, metric=MetricName(namespace=ns, name=counter), labels={}): 4



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