[BUG] Tracing is broken for EventHub binder

[lmolkova]

Describe the bug
Following the eventhub binder app doc with tracing enabled: message span is not correlated to incoming request.

This is a reactor context propagation issue and we'd need to find

• way to manually pass context (if possible)
• make magical propagation work

This issue is mostly created for investigation purposes.

It does not affect non-binder scenario (e.g. this one)

To Reproduce

1. create sample app
2. add application insights agent and configure azure sdk tracing
3. send/receive/process message
4. check message span - it is not correlated to the incoming request

Expected behavior
message span is created as a child of incoming request.

Screenshots

Actual: Two traces (with 2 trace-ids)

Expected: 1 trace (created without binder)

Setup (please complete the following information):

• OS: windows
• IDE: IntelliJ
• Library/Libraries: com.azure:azure-core:1.17.0, com.azure:azure-core:1.17.0, com.azure:azure-core-tracing-opentelemetry:1.0.0-beta12, com.azure.spring:azure-spring-cloud-stream-binder-eventhubs:2.5.0, applicationinsights-agent-3.1.1

Additional context
Context is available when sending messages to supply sink

But lost when a message is instrumented

Stacktrace shows the attempt of otel agent to propagate reactor context, but it's not successful.

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Bug Description Added
• Repro Steps Added
• Setup information Added

[stliu]

@lmolkova Hi is this still valid?

[ghost]

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!