[
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 pull-request-available stale-minor (was:
auto-deprioritized-major pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, pull-request-available,
> stale-minor
> 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)
