guring Prometheus metrics.
>
>
>
> Chris
>
>
>
>
>
> *From: *Ori Popowski
> *Date: *Monday, June 22, 2020 at 12:22 PM
> *Cc: *user
> *Subject: *[EXTERNAL] Re: Renaming the metrics
>
>
>
> Thanks for answering.
>
>
>
> Unrelated to Fli
generic flink-approved method of configuring Prometheus metrics.
Chris
From: Ori Popowski
Date: Monday, June 22, 2020 at 12:22 PM
Cc: user
Subject: [EXTERNAL] Re: Renaming the metrics
Thanks for answering.
Unrelated to Flink, but if anyone knows a way to rename the metrics inside
Prometheus I&#
Thanks for answering.
Unrelated to Flink, but if anyone knows a way to rename the metrics inside
Prometheus I'd appreciate if you can share.
About the push gateway - I think I'll stick with the pull options because
it looks like a better fit to the use case
On Mon, Jun 22, 2020 at 4:47 PM Chesna
There's currently no way to change this.
A related enhancement was proposed on FLINK-17495 that would at least
allow you to attach a custom label, but the initial implementation
wasn't general enough.
On 22/06/2020 15:08, Arvid Heise wrote:
Hi Ori,
I see that the PrometheusPushGatewayReport
Hi Ori,
I see that the PrometheusPushGatewayReporter [1] has an option for a job
name, maybe you can use that.
I'm also including Chesnay who probably has more ideas.
[1]
https://ci.apache.org/projects/flink/flink-docs-master/monitoring/metrics.html#prometheuspushgateway-orgapacheflinkmetricspro
I have two Flink clusters sending metrics via Prometheus and they share all
the metric names (i.e.
flink_taskmanager_job_task_operator_currentOutputWatermark).
I want to change the flink_ prefix to something else to distinguish between
the clusters (maybe the job-name).
How can I do it?
Thanks.
