Eventhub Opentelemetry Trace exception: "'MessageProperties' object has no attribute 'setdefault'"

[erewok]

• Package Name: azure-eventhub
• Package Version: 5.10.1
• Operating System: Linux-Debian (docker container)
• Python Version: 3.11.1

Describe the bug
Today in an experiment with adding tracing spans to our EventhubProducerClient calls, I followed a helpful example provided by the package azure-core-tracing-opentelemetry.

After some tracing spans were produced, I noticed an exception in the logs (but these did not prevent events from being published):

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/opentelemetry/trace/__init__.py", line 573, in use_span
    yield span
  File "/usr/local/lib/python3.11/site-packages/azure/eventhub/_utils.py", line 181, in trace_message
    event.properties.setdefault(
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'MessageProperties' object has no attribute 'setdefault'

In the _utils.py module, there's a function called trace_message with a few lines like this:

                if not event.properties:
                    event.properties = dict()
                event.properties.setdefault(
                    b"Diagnostic-Id", message_span.get_trace_parent().encode("ascii")
                )

Here, if event.properties is truthy, then it will not be a Python dict (as in my case), and instead it's an instance of MessageProperties from the uamqp library, which has no setdefault function.

To fix it, we could indent setdefault under the if not event.properties and add an else that sets the property differently for MessageProperties.

I would be happy to submit a PR for this change if it is useful.

To Reproduce
Steps to reproduce the behavior:

1. Follow the example for instrumenting an EventhubProducerClient
2. Produce some events.
3. Load tracing span waterfall graph matching this trace id.
4. See exception screenshot below

Screenshots

Expected behavior
No exceptions when instrumenting Eventhub calls with opentelemetry tracing spans.

[kristapratico]

Hi @erewok thanks for the detailed issue, we'll take a look and get back to you as soon as possible.

[swathipil]

Hi @erewok - Thanks for the investigation! It was very helpful in helping reproduce/track down the bug. We've made a few big changes recently to the SDK, so the fix will be a little bit more complex. We're working on it right now and will keep you posted on any updates. Thanks!

[erewok]

@swathipil, great! Glad to hear it and glad that this issue was useful. Thanks for following up.