[
https://issues.apache.org/jira/browse/FLINK-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002579#comment-17002579
]
Yang Wang commented on FLINK-15356:
-----------------------------------
Hi [~x1q1j1],
I have no doubt that this is a useful feature. What i means is whether we could
add the {{clusterId}} to metrics. When deploying on Yarn, it is usually set to
applicationId. In standalone and kubernetes, the clusterId could be specified
separately. In my opinion, the {{clusterId}} is the unique identifier of a
Flink cluster.
> Add applicationId to existing flink metrics running on yarn
> -----------------------------------------------------------
>
> Key: FLINK-15356
> URL: https://issues.apache.org/jira/browse/FLINK-15356
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Reporter: Forward Xu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When sending metrics to Prometheus, these systems have only the Flink job ID,
> and the Flink job ID is UUID, which cannot be associated with the application
> job on the yarn. Therefore, we need to increase the applicationId when
> running on yarn. This helps us to accurately find the corresponding job on
> yarn when the metric is abnormal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
