o-lovgren

> [@rads-1996](https://github.com/rads-1996) Can we get an update on this? Today, my Function App deployments are failing on Azure with the below stack trace, which seem to be coming from just...

Hi @hallvictoria I don't know if it makes a difference, but we are running Premium v3 as the hosting plan.

I can also confirm that we are using the exact same dependency list when using opentelemetry-api in requirements.txt. This was taken from my pipeline output: PyJWT-2.10.1 aiohappyeyeballs-2.6.1 aiohttp-3.13.2 aiosignal-1.4.0 annotated-types-0.7.0...

Today I also tried pinning all my relevant opentelemetry packages as stated here: https://github.com/Azure/azure-functions-python-worker/issues/1808#issuecomment-3612223279 I used the following in my requirements.txt: azure-monitor-opentelemetry==1.8.2 opentelemetry-instrumentation-logging==0.59b0 opentelemetry-api==1.38.0 I can see that these were...

> I tried creating a 3.12 app on Premium (function runtime version 4.1045) with those dependencies & import statement, but I still wasn't able to reproduce the issue. > >...

Also, these are the import statements that I am using: from azure.monitor.opentelemetry import configure_azure_monitor from opentelemetry import trace from opentelemetry.propagate import extract from opentelemetry.trace import SpanKind from opentelemetry.instrumentation.logging import LoggingInstrumentor

> > Is 404 the expected return status > > Yep, thanks for that. > > Two things to be called out here: > > * [Remote build](https://learn.microsoft.com/en-us/azure/azure-functions/functions-deployment-technologies?tabs=linux#remote-build) is not...