davsclaus commented on PR #30220:
URL: https://github.com/apache/camel/pull/30220#issuecomment-6971552530

   @squakez I agree that running both is not something we recommend, and the 
docs can say so. But there are special moments where it is useful for a while, 
for example when migrating from Micrometer to OpenTelemetry metrics (or back), 
and comparing what the two report for the same routes before switching over. A 
hard check at startup would block exactly that.
   
   Whatever we decide there, this PR is still the right fix: two route policies 
storing their per-exchange timer under the same exchange property name is a 
latent bug either way, and today the combination does not fail cleanly, it logs 
a `ClassCastException` WARN for every exchange. Giving each policy its own 
property name (as the camel-metrics route policy already does) makes it work 
when someone does combine them.
   
   So my suggestion is to merge this fix, and if we want to steer users away 
from running both, do it with a note in the docs (or at most an INFO/WARN log 
at startup) rather than refusing to start. Which check for the telemetry 
components did you have in mind? I could not find one that refuses a second 
tracer, so I may be looking in the wrong place.
   
   _Claude Code on behalf of davsclaus_
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to