azure-monitor-opentelemetry broken with the recent v1.32.0 release of opentelemetry-api and opentelemetry-sdk

[mindspin]

• Package Name: azure-monitor-opentelemetry
• Package Version: 1.6.6
• Operating System: Windows
• Python Version: 3.10

Describe the bug
The new 1.32.0 version of opentelemetry-api and opentelemetry-sdk brings a breaking change that removes the get_dist_dependency_conflicts() function used by azure-monitor-opentelemetry.

To Reproduce
Steps to reproduce the behavior:

1. pip install azure-monitor-opentelemetry
2. from azure.monitor.opentelemetry import configure_azure_monitor

Expected behavior
The import of 'configure_azure_monitor' shouldn't fail.

Screenshots

pip install azure-monitor-opentelemetry

>> from azure.monitor.opentelemetry import configure_azure_monitor
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File ".../lib/site-packages/azure/monitor/opentelemetry/__init__.py", line 7, in <module>
    from azure.monitor.opentelemetry._configure import configure_azure_monitor
  File ".../lib/site-packages/azure/monitor/opentelemetry/_configure.py", line 12, in <module>
    from opentelemetry.instrumentation.dependencies import (
ImportError: cannot import name 'get_dist_dependency_conflicts' from 'opentelemetry.instrumentation.dependencies' (.../lib/site-packages/opentelemetry/instrumentation/dependencies.py)

Workaround
Explicitly installing opentelemetry-sdk at a previous version, ie 1.31.1, fixes the issue.

Additional context
The setup.py file specifies dependency versions for opentelemetry-api and opentelemetry-sdk as ~=1.26. This allows any version within the range >=1.26.0 and <2.0.0 to be installed, as the ~= specifier ensures compatibility within the same major version. As a result, pip installs version 1.32.0, which falls within this range.

• Make auto instrumentation use the same dependency resolver as manual instrumentation does open-telemetry/opentelemetry-python-contrib#3202
• opentelemetry-instrument 0.53b0 release breaks azure-monitor-opentelemetry open-telemetry/opentelemetry-python-contrib#3415

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @hectorhdzg @jeremydvoss @lzchen.

[github-actions]

Hello @mindspin. I'm an AI assistant for the azure-sdk-for-python repository. I found a solution for your issue!

• The recent opentelemetry-api/sdk v1.32.0 release has removed the get_dist_dependency_conflicts() function, which is currently used by azure-monitor-opentelemetry.

• As a workaround, please pin your opentelemetry-sdk version to 1.31.1 (or another compatible version) until we update our dependency requirements.

• We are aware of the issue and are planning a patch release to update our setup to constrain the opentelemetry dependencies appropriately. For more details on the breaking change, see opentelemetry-python-contrib PR#3202.

• For additional instructions on configuring Azure Monitor with OpenTelemetry, refer to the README.

This should solve your problem, if it does not feel free to reopen the issue.

[neeagl]

Our deployment just got failed as well because of this update. On digging, it appears in the package: opentelemetry-instrumentation
Have pinned it to v0.52b1 and it worked!

[jeremydvoss]

Fixed in azure-monitor-opentelemetry==1.6.7

[jeremydvoss]

Recommend closing, but we can leave open for a bit in case anyone has questions.

[Rexeh]

Fixed in azure-monitor-opentelemetry==1.6.7

Thanks for such speedy response! Confirmed all good no more failed runs.