[
https://issues.apache.org/jira/browse/CAMEL-26565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Mariani resolved CAMEL-26565.
--------------------------------------
Resolution: Fixed
_Claude Code on behalf of Croway_
Fixed by:
- main (4.24.0): https://github.com/apache/camel/pull/29139
- camel-4.22.x (4.22.3): https://github.com/apache/camel/pull/29140, a straight
cherry-pick
- camel-4.18.x (4.18.6): https://github.com/apache/camel/pull/29141, with only
the CamelContext.getRoute() part. 4.18.x does not have the getOrCreateTimer()
registry search added by CAMEL-23719: its timers already use register().
MicrometerExchangeEventNotifier no longer searches the meter registry on
exchange events: it uses Timer.builder().register() instead of find(). It also
decides the kamelet/route-template skip once per route, instead of calling
CamelContext.getRoute() on every event.
> [camel-micrometer] Regression and reduced metrics retrieval performances
> ------------------------------------------------------------------------
>
> Key: CAMEL-26565
> URL: https://issues.apache.org/jira/browse/CAMEL-26565
> Project: Camel
> Issue Type: Bug
> Reporter: Pasquale Congiusti
> Assignee: Federico Mariani
> Priority: Major
> Fix For: 4.18.6, 4.22.3, 4.24.0
>
>
> In CAMEL-26415 we had worked to a performance issue reported. However the fix
> was not enough. During analysis it turns out that the performance drop was
> really caused by another regression introduced in [1] and correctly spotted
> in [2].
> So, a solution would be to fix the regression, likely as proposed in the PR's
> comment ([2]).
>
> [1] [https://github.com/apache/camel/pull/23864] (CAMEL-23719)
> [2] https://github.com/apache/camel/pull/28729#issuecomment-6576343651
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
