[
https://issues.apache.org/jira/browse/GERONIMO-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17935820#comment-17935820
]
Arne Limburg commented on GERONIMO-6880:
----------------------------------------
[~romain.manni-bucau] Digging further into it, I found some more problems
mapping the metrics of Microprofile Metrics into OpenTelemetry Metrics.
Metrics like "Timer" are not present in OpenMetrics and thus not in prometheus
([https://prometheus.github.io/client_java/getting-started/metric-types/|https://prometheus.github.io/client_java/getting-started/metric-types/),]).
Maybe it should be reported as "Summary" or as "Histogram". Concurrent Gauge
propably should be reported as Gauge. I don't know, how "Metered" matches into
the OpenMetrics types.
I would implement all that, we only have to agree, how to map the Microprofile
Metrics into prometheus metrics.
> [Metrics] Using a histogram leads to error in prometheus
> --------------------------------------------------------
>
> Key: GERONIMO-6880
> URL: https://issues.apache.org/jira/browse/GERONIMO-6880
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Metrics
> Reporter: Arne Limburg
> Priority: Major
>
> When using a histogram in geronimo-metrics 1.0.6, Prometheus 3.2.0 gives the
> error:
> invalid metric type "summary histogram"
>
> I can provide a fix, but I don't know, how the correct behavior would be.
> Just delete the line, that creates that "summary histogram" metric type?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
