[
https://issues.apache.org/jira/browse/CAMEL-22941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18060279#comment-18060279
]
Pasquale Congiusti commented on CAMEL-22941:
--------------------------------------------
All investigation points to some problem in the camel-observation component.
This component is based on an older camel-tracing technology we're planning to
deprecate in favor of camel-telemetry components. As an immediate suggestion,
while we try to fix the root cause, you may try to replace the following
dependency with the newer one:
{code}
<!-- dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-observation-starter</artifactId>
</dependency -->
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-micrometer-observability-starter</artifactId>
</dependency>
{code}
and the related enabling configuration:
{code}
# tracing:
# enabled: true
telemetry:
enabled: true
{code}
In the long run it's something you may need to do, so, feel free to try this
workaround (and likely long term solution) while the problem on this component
is fixed.
{code}
> "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)
