[
https://issues.apache.org/jira/browse/FLINK-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-15356:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor
pull-request-available (was: auto-deprioritized-major pull-request-available
stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> pull-request-available
> Time Spent: 20m
> 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.20.1#820001)
