Evaluate changing OTEL_INSTRUMENTATION_MESSAGING_EXPERIMENTAL_RECEIVE_TELEMETRY_ENABLED to true

[SylvainJuge]

Upstream java instrumentation provides: OTEL_INSTRUMENTATION_MESSAGING_EXPERIMENTAL_RECEIVE_TELEMETRY_ENABLED which is set to false by default.

Sending JMS message synchronously when set to false (default for now)

The JMS receiving span is part of the trace that sent the message, as if it was a direct parent-child relationship.

Sending JMS message synchronously when set to true (opt-in for now)

The "publish" span is created with two span links, which allow to navigate to the related trace where the message is processed.

What looks a bit weird and probably a bit of investigation is that when this config option is set to true we have two spans created when receiving the message:

When we look at the span links of the sending span, we have :

---

How to reproduce:

• use changes from enhance messaging testapp #907 (or wait until it's merged)
• set OTEL_INSTRUMENTATION_MESSAGING_EXPERIMENTAL_RECEIVE_TELEMETRY_ENABLED to true or false
• start the test application, for example directly from the IDE (I did not manage to make it start correctly from the CLI, there is probably still a packaging/missing dependency in the executable jar)
• call curl http://localhost:8080/messages/send/async-queue, this will trigger the transaction visible in he screenshots above.