Failed to derive Resource from Tracer Provider: 'ProxyTracerProvider' object has no attribute 'resource'

[TaylorN15]

• Package Name: azure-monitor-opentelemetry-exporter
• Package Version: 1.0.0b29
• Operating System: Linux (Azure App Service)
• Python Version: 3.10

Describe the bug
Recently I have noticed a large amount of exceptions being thrown by azure-monitor-opentelemetry-exporter
which seem to be related to this change.

2024-09-19T00:09:19.214845698Z: [ERROR]  Traceback (most recent call last):
2024-09-19T00:09:19.214853498Z: [ERROR]    File "/tmp/8dcd83d242adfa1/antenv/lib/python3.10/site-packages/azure/monitor/opentelemetry/exporter/export/trace/_exporter.py", line 91, in export
2024-09-19T00:09:19.214876499Z: [ERROR]      resource = tracer_provider.resource # type: ignore
2024-09-19T00:09:19.214882599Z: [ERROR]  AttributeError: 'ProxyTracerProvider' object has no attribute 'resource'

To Reproduce
I am not sure what is causing the exception to occur, but looking at the log stream from the App Service, it appears very frequently, so I assume it's whenever it's trying to log to Azure Monitor/App Insights.

Expected behavior
No exceptions

Additional context
Add any other context about the problem here.
I am also using some other otel packages as below

opentelemetry-instrumentation-aiohttp-client
opentelemetry-instrumentation-httpx
opentelemetry-instrumentation-requests
opentelemetry-instrumentation-openai

[github-actions]

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

[Pinqvin]

We noticed this problem in our environment as well (Linux App Service, Python 3.12). Seems like version 1.0.0b29 introduced some breaking changes or something else is wrong here. We fixed the issue by downgrading both azure-monitor-opentelemetry packages:

azure-monitor-opentelemetry==1.6.1 
azure-monitor-opentelemetry-exporter==1.0.0b28

Ran into this issue and solution via Stack Overflow

[lzchen]

@TaylorN15 @Pinqvin

Could you share a code snippet of the logic you are using? I mostly want to see if you are setting the global TracerProvider before the AzureMonitorTraceExporter.

[lzchen]

I've put out a potential fix for the issue, apologies about the breaking behavior.

#37469