Opentelemtry 1.39.0 incompatible with azure-monitor-opentelemetry-exporter: 1.0.0b45

[jabbera]

Describe the bug
Newest opentelemtry removed LogData used by azure monitor. See:
https://github.com/open-telemetry/opentelemetry-python/blob/6de910fc6f9a3c5f9c762f592426fd2191e88174/CHANGELOG.md?plain=1#L28

To Reproduce
Steps to reproduce the behavior:
pip install opentelemetry-sdk>=1.39.0 azure-monitor-opentelemetry-exporter==1.0.0b45

python -c 'from azure.monitor.opentelemetry.exporter.export.logs._exporter import AzureMonitorLogExporter'

../../_temp/.tox/py311/lib/python3.11/site-packages/azure/monitor/opentelemetry/exporter/__init__.py:7: in <module>
    from azure.monitor.opentelemetry.exporter.export.logs._exporter import AzureMonitorLogExporter
../../_temp/.tox/py311/lib/python3.11/site-packages/azure/monitor/opentelemetry/exporter/export/logs/_exporter.py:14: in <module>
    from opentelemetry.sdk._logs import LogData
E   ImportError: cannot import name 'LogData' from 'opentelemetry.sdk._logs' (/agent/_work/_temp/.tox/py311/lib/python3.11/site-packages/opentelemetry/sdk/_logs/__init__.py)

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @hectorhdzg @JacksonWeber @jeremydvoss @Karlie-777 @lzchen @MSNev @rads-1996.

[github-actions]

Hi @jabbera, I'm an AI Support assistant here to help with your issue. While the Azure SDK team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

• The issue stems from a breaking change in OpenTelemetry 1.39.0 where LogData was removed, which the exporter (1.0.0b45) still expects.
• For now, consider using an earlier version of the OpenTelemetry SDK that still includes LogData to maintain compatibility with the exporter.
• Keep an eye on the release notes for the exporter to learn when a new package version will support the updated OpenTelemetry SDK.
• For more details on the breaking changes in OpenTelemetry 1.39.0, please refer to the changelog: OpenTelemetry Python CHANGELOG.

The Azure SDK team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

[rads-1996]

@jabbera Thank you for bringing this up. We will release a new version of the exporter tomorrow that will use the OTEL version which is stable while we continue to get breaking changes from opentelemetry. Will keep you posted once release is done and ready to be used. Meanwhile, can you use version 1.38 to prevent these errors?

[jabbera]

Meanwhile, can you use version 1.38 to prevent these errors?

Yup!

[rads-1996]

Meanwhile, can you use version 1.38 to prevent these errors?

Yup!

Thank you very much :). Will keep you posted once we release the new version of the exporter.

[rads-1996]

@jabbera We have released a new version of the exporter - azure-monitor-opentelemetry-exporter version 1.0.0b46. Please try using that and let us know if you still get any errors.