You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kyle Weaver (Jira)" <ji...@apache.org> on 2020/05/14 17:58:00 UTC

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

Kyle Weaver created BEAM-9997:
---------------------------------

             Summary: 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
            Assignee: Kyle Weaver


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)