[
https://issues.apache.org/jira/browse/FLINK-9187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516760#comment-16516760
]
ASF GitHub Bot commented on FLINK-9187:
---------------------------------------
Github user lamber-ken commented on the issue:
https://github.com/apache/flink/pull/5857
@zentol, @tillrohrmann, cc
I don't think there is a relationship between `FLINK-9543` and `FLINK-9187`.
At present, the focus of our discussion is on the job name of pushgateway.
My point is that there is no need to use JMID or TMID to form the job name
of pushgateway, because the job name of pushgateway is just used to distinguish
different services(like TM or JM and), and prevent the same metrics from being
covered, it doesn't make sense for metrics data.
A minimal reproducible example, two flink cluster, each cluster includes
one JM and three TMs.



> add prometheus pushgateway reporter
> -----------------------------------
>
> Key: FLINK-9187
> URL: https://issues.apache.org/jira/browse/FLINK-9187
> Project: Flink
> Issue Type: New Feature
> Components: Metrics
> Affects Versions: 1.4.2
> Reporter: lamber-ken
> Priority: Minor
> Labels: features
> Fix For: 1.6.0
>
>
> make flink system can send metrics to prometheus via pushgateway.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)