You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/02/07 13:57:00 UTC

[jira] [Created] (FLINK-8592) LatencyMetric scope should include operator names

Chesnay Schepler created FLINK-8592:
---------------------------------------

             Summary: LatencyMetric scope should include operator names
                 Key: FLINK-8592
                 URL: https://issues.apache.org/jira/browse/FLINK-8592
             Project: Flink
          Issue Type: Improvement
          Components: Metrics
    Affects Versions: 1.5.0
            Reporter: Chesnay Schepler


As of FLINK-7608 the latency metric scope contains the operator ID and subtask index of both the latency marker origin and recipient. We  do not however expose the operator names.

 

This is inconsistent with existing metrics about operators (although this is a big can of worms since various task-level fields like executionId are also missing), but more importantly does not allow for any stable identification across job submissions, as the IDs always change.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)