Github user yew1eb commented on the issue:
https://github.com/apache/flink/pull/5161
Yes, in our production environment, we report and store all metrics to an
external Time series database for alarm and visual presentation.
When the job is started, we will store the edge structure of the job's
logical plan: eg. <Unique_job_source_id, jobName, operatorA, operatorB>.
For the latency metrics, we hope to include the operatorName instead of the
operatorID in the tags. because operatorID will change if the job redeploys,
the history's latency metrics data for the job will be hard to match and no
latency statistics will be observed in our visualization panel.
---
