[
https://issues.apache.org/jira/browse/CAMEL-22941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18060304#comment-18060304
]
Pasquale Congiusti commented on CAMEL-22941:
--------------------------------------------
Yeah, it's a quite confusing, reason why we have started a work to clean
everything. However we cannot drop easily the older implementation to avoid
breaking compatibility in a major version, so we need to survive with these
duplications around for a while.
So, what I was proposing is this one
https://camel.apache.org/components/4.18.x/others/micrometer-observability.html,
which aims to replace the observation which is the one you've linked to.
Unfortunately, although the component is known as camel-observation, it links
to a component named "Micrometer Observability". That's why the new
implementation is instead known as "Micrometer Observability 2", which is the
one I propose and I've linked to.
> "POST_Exchange____Id__" metrics
> -------------------------------
>
> Key: CAMEL-22941
> URL: https://issues.apache.org/jira/browse/CAMEL-22941
> Project: Camel
> Issue Type: Bug
> Components: camel-metrics
> Affects Versions: 4.16.0, 4.18.0
> Reporter: David J. M. Karlsen
> Assignee: Pasquale Congiusti
> Priority: Minor
> Fix For: 4.19.0
>
> Attachments: Screenshot 2026-02-01 at 14.33.37.png
>
>
> When visiting the spring-boot prometheus metrics page, there are tons of
> metrics named
> POST_Exchange____Id__9F24210ADD30EA2_0000000000000001___Headers___accept_application_xml__authori.....___total,
> i.e. a unique metric name per request.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
