[
https://issues.apache.org/jira/browse/FLINK-22164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320795#comment-17320795
]
Till Rohrmann commented on FLINK-22164:
---------------------------------------
Hi [~qqibrow], thanks for reporting this issue. Have you seen the
[documentation about Flink's
metrics|https://ci.apache.org/projects/flink/flink-docs-stable/ops/metrics.html#scope].
If I am not mistaken, then you should be able to insert the {{job_id}} into
the scope of the JM metrics. Would this be enough to solve your problem? If
not, then you would have to explain it a bit more in detail.
> Add jobId and JobName variable to JobManager metrics in per-job deployment
> mode
> -------------------------------------------------------------------------------
>
> Key: FLINK-22164
> URL: https://issues.apache.org/jira/browse/FLINK-22164
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Reporter: Lu Niu
> Priority: Minor
>
> We expose all flink metrics to external system for monitoring and alerting.
> However, JobManager metrics only have one variable <hostname>, which is not
> enough to target to one job when job is deployed to YARN. If flink job runs
> in per-job mode, which ensure one job per cluster, we can add jobId and
> JobName to JobMananger metrics.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
