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

Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/01/31 11:12:00 UTC

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

     [ https://issues.apache.org/jira/browse/FLINK-8592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-8592.
--------------------------------
    Resolution: Won't Do

Won't do at this point in time. Maybe in the future.

> LatencyMetric scope should include operator names
> -------------------------------------------------
>
>                 Key: FLINK-8592
>                 URL: https://issues.apache.org/jira/browse/FLINK-8592
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics
>    Affects Versions: 1.5.0
>            Reporter: Chesnay Schepler
>            Priority: Major
>
> 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
(v8.3.4#803005)