OpenTelemetry DataDog exporter is broken because of breaking change in this package.

[owais]

This package introduced some breaking changes that caused OpenTelemetry Python's DataDog exporter to break as well. We've pinned ddtrace dependency to the last know working version to make things work again. Opening this issue to let maintainers here know about it so they can fix the Otel exporter as they see fit.

open-telemetry/opentelemetry-python-contrib#400

Thanks.

[Kyle-Verhoog]

Thanks for the quick fix @owais! We'll look into fixing the exporter to remove the pin 🙂

[phillipuniverse]

@Kyle-Verhoog what's the status here? And @owais is there a list of what the breaking changes are? I am interested in attempting a fix.

I'm running into #1413 which is resolved by #2459 and only available in 0.50.0+ of ddtrace.

[phillipuniverse]

@Kyle-Verhoog @owais any update here?

[pj-datadog]

@phillipuniverse This feature is currently in beta. Can you please reach out to Datadog support if it doesn't work as you expect. Thank You

[phillipuniverse]

@pj-datadog I am a bit confused by your comment. What exactly is in beta and how would I test it to see if it behaves as I would expect?

OpenTelemetry still pins the version of ddtrace to 0.47.0. My original question was why, and I’m still not sure why.

What am I missing?

[pj-datadog]

Hi @phillipuniverse, pardon the ambiguity there. The OTel Datadog Python Span Exporter that this issue talks about is still in beta. We invite you to reach out to Datadog support, we can learn more about the issue you are facing and your intended use of the library. We might also have an alternate option for you to test/use for your use-case.

As for your original question, we are still in the process of building and validating this feature. Before we release anything for our users, we want to make sure we are able to provide best support to our users on all of their use-cases. Thank you for being a valued DataDog customer!

[phillipuniverse]

Based on open-telemetry/opentelemetry-python-contrib#932 (comment) and the exporter being deprecated this issue can likely be closed.

[majorgreys]

Thanks @phillipuniverse for following up here. As you point out, the exporter (which depended on this library) is deprecated.