squakez commented on PR #16386:
URL: https://github.com/apache/camel/pull/16386#issuecomment-2503764758
I have gone through a bit more troubleshooting about this. I've added some
logging traces and I am not able to reproduce the problem on Spring Boot
runtime. Starting a simple timer to log seems to create a new span at each
exchange with actual 4.9.0-SNAPSHOT code:
```
2024-11-27T13:22:20.859+01:00 DEBUG 446184 --- [ - timer://yaml]
[69da4c773180c20d932deb3dbda91b50-a9710cbc4e5acb99]
org.apache.camel.tracing.Tracer : Tracing: start server
span=OpenTelemetrySpanAdapter [baggage={},
span=PropagatedSpan{ImmutableSpanContext{traceId=69da4c773180c20d932deb3dbda91b50,
spanId=a9710cbc4e5acb99, traceFlags=00,
traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=true}}] with
parent null
....
2024-11-27T13:22:50.841+01:00 DEBUG 446184 --- [ - timer://yaml]
[af918b6f238227c77a401fbb6ed07dff-0306f19c52754b1b]
org.apache.camel.tracing.Tracer : Tracing: start server
span=OpenTelemetrySpanAdapter [baggage={},
span=PropagatedSpan{ImmutableSpanContext{traceId=af918b6f238227c77a401fbb6ed07dff,
spanId=0306f19c52754b1b, traceFlags=00,
traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=true}}] with
parent null
```
What I have verified is that on Camel Main runtime we don't have any
propagation at all, which is something that would require some attention. On
Spring Boot, there is some injection that make this to work. How are you
running the application? I wonder if the way it is executed is influencing the
final behavior.
--
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: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
