Distributed Tracing / OpenTelemetry: Testing Solace Implementation and trying our own
we are trying to implement Distributed Tracing in our Solace Environment.
We are struggling to get your implementation (https://solace.community/discussion/1553/distributed-tracing-is-now-generally-available#latest) to run correctly. We have some questions:
- In your presentation video (https://youtu.be/0uwy26zPc-o?t=1607) you’re showing a Trace, with a Span from LegacyOrderManagementSystem. The trace contains other Spans (i.e. vmr-133-54), which are coming from the Solace Broker. This means a Context Propagation must have happened. Later it is the other way around: There’s a Span created by a solace broker and a custom open telemetry service is writing a span in the same trace. How is this implemented?
- We tried to implement Context Propagation on our own: We save the Span Context in the message we send in solace (in the correlationID), so we can propagate the context in a distributed environment. Are you doing it the same way? Is there a better way?
- Also we are using Nested Spans (parent<->child relationship) to connect spans. Are you doing the same?