[
https://issues.apache.org/jira/browse/FLINK-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002381#comment-17002381
]
Forward Xu commented on FLINK-15356:
------------------------------------
hi, [~fly_in_gis] Such application scenarios. We use Prometheus to monitor
metrics to alert. How can I find this running job in yarn by jobID? Of course,
this problem can also be solved by specifying a unique jobName. But jobName is
not always unique. There is no appID indicator for Kubernetes / Mesos and it
will not be displayed.
> 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)
