You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Lim Qing Wei (Jira)" <ji...@apache.org> on 2022/11/10 17:11:00 UTC
[jira] [Updated] (FLINK-29984) Flink Histogram not emitting min and max when using Prometheus Reporter
[ https://issues.apache.org/jira/browse/FLINK-29984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lim Qing Wei updated FLINK-29984:
---------------------------------
Description:
Flink Histogram when using the Prometheus Metrics Reporter only produces
* quantiles of 0.5, 0,75, 0.95, 0.98, 0.99, 0.999
* count
I think it would be a good idea to also produce min and max, as they are already available in the state, we can model it as p0 and p1.0
was:
I am currently registering a Flink Histogram and using the Prometheus Metrics Reporter to send this metric to our Time Series Data Storage. When Prometheus grabs this metric and converts it to the "summary" type, there is no sum found (only the streaming quantiles and count). This is causing an issue when our metrics agent is attempting to capture the Flink Histogram/Prometheus Summary.
I was wondering if in a newer version (than 1.13.6) the histogram sum is computed by Flink and what that version would be? If not, is there any work around so that a Flink histogram can emit all 3 elements (quantiles, sum, and count) in Prometheus format?
> Flink Histogram not emitting min and max when using Prometheus Reporter
> -----------------------------------------------------------------------
>
> Key: FLINK-29984
> URL: https://issues.apache.org/jira/browse/FLINK-29984
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Metrics
> Affects Versions: 1.13.6
> Reporter: Lim Qing Wei
> Priority: Major
>
> Flink Histogram when using the Prometheus Metrics Reporter only produces
> * quantiles of 0.5, 0,75, 0.95, 0.98, 0.99, 0.999
> * count
>
> I think it would be a good idea to also produce min and max, as they are already available in the state, we can model it as p0 and p1.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)