Pasquale Congiusti

Consider that in async components, there can be spans that looks similar but are different as one is outgoing and the other incoming. Compare the EVENT_SENT and EVENT_RECEIVED to make...

More than a regression is a change in the service used. I think that lately we're using `camel-quarkus-opentelemetry2` which is different from `camel-quarkus-opentelemetry`. There could be differences in number of...

Thanks for clarifying. So, I understand that the older otel extension was patching the tracing behavior for some reason I ignore. However with the newer implementation the context propagation is...

That's the point. IMO, they are not identical. One is generated by Camel, the other is generated by the dependency. And the hint that they are different is even more...

Likely depends on https://github.com/quarkusio/quarkus/issues/50466

The bug is likely still there. I don't have any further time to dedicate on it. Feel free to do any patch on our extension, although it does not sound...

I think we have an e2e test covering the context propagation scenario [1]. The point is that, since we do not longer rely on thread context propagation, as it happened...

Hi folks. I think we have several issues mixed here. The one on our control on core was reported in https://issues.apache.org/jira/browse/CAMEL-22648. In certain telemetry implementations we're missing to propagate the...

Hello. I've made a deep analysis of the problem and I've come up to the conclusion that, this is not a bug on our side. All details in https://issues.apache.org/jira/browse/CAMEL-22648 Let...

Yes. From a Camel maintainers perspective, we cannot do things different from the standard specification. From my side I'm trying to fix the agent in order to have that available...