Distributed Tracing Demo

Options
kilbac
kilbac Member Posts: 6

Hi,

we are currently testing the Distributed Tracing Feature [1].

After some initial difficulties we got it running. We are using the following docker containers:

  • jaegertracing/all-in-one:1.39
  • otel/opentelemetry-collector-contrib:0.64.1
  • solace/solace-pubsub-standard:10.2.0.26

We setup the telemetry over the GUI and are using the "Try me" function in the GUI to send a message to the traced queue.

Jaeger shows a Trace for the sending of the message.

We then use a Java Client to subscribe to the queue, take a message and acknowledge it. None of this is displayed in the Jaeger GUI.

(If we use the Java Client to send a message to the queue, it will get displayed)


So we are wondering:

  • Are we doing something wrong?
  • What exact features does the distributed tracing feature offer? Does it show a full lifecycle of a message (send/read/ack) as one trace?


Thanks in advance. Kind regards,

Kilian


[1] https://solace.community/discussion/1553/distributed-tracing-is-now-generally-available

Best Answer

  • TomF
    TomF Member, Employee Posts: 408 Solace Employee
    #2 Answer ✓
    Options

    Hi @kilbac,

    Currenty DT only supports the sending trace landing on queues. Further features, such as egress, then context propagation, will be in later releases.

Answers

  • TomF
    TomF Member, Employee Posts: 408 Solace Employee
    #3 Answer ✓
    Options

    Hi @kilbac,

    Currenty DT only supports the sending trace landing on queues. Further features, such as egress, then context propagation, will be in later releases.

  • Tamimi
    Tamimi Member, Administrator, Employee Posts: 500 admin
    Options

    Stay tuned as we add more functionalities! You're feedback is valuable 👍