Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-8592

LatencyMetric scope should include operator names

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Won't Do
    • 1.5.0
    • None
    • Runtime / Metrics
    • None

    Description

      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.

      Attachments

        Issue Links

          blocks

          New Feature - A new feature of the product, which has yet to be developed. FLINK-9653 Add operator name to latency metrics

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is duplicated by

          New Feature - A new feature of the product, which has yet to be developed. FLINK-9653 Add operator name to latency metrics

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              Unassigned Unassigned
              chesnay Chesnay Schepler
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: