OpenTelemetry integration with Node.js Function Apps, seems like spans are missing

I am integrating OpenTelemetry with some Azure Function Apps using Node.js for the first time with Zipkin. Zipkin is running as a container app I am hosting on Azure. I instrumented my app (specifically, an http app that responds to POSTs) and tested the _app_ (they pushed traces to Zipkin running on my Azure container app) locally in a Docker container, and it worked great. Multiple levels of spans and everything was in expected order. Here is a screenshot of the expected output:


When I deployed this app to Azure, the tracing and spans were completely incorrect. Many spans are seemingly not being recorded, and there appear to be others sort of hanging loose off of the parent span. Screenshot of what tracing looks like _after_ deploying to Azure:


I tried going over [the guide](https://learn.microsoft.com/en-us/azure/azure-functions/opentelemetry-howto?tabs=app-insights&pivots=programming-language-javascript) as well, but no luck. I also tried adding the AlwaysOnSampler indicated in [this issue](https://github.com/open-telemetry/opentelemetry-js/issues/3057), but that also didn't seem to help.

I read some other Github issues here:
https://github.com/Azure/azure-functions-dotnet-worker/issues/2543
https://github.com/Azure/azure-functions-dotnet-worker/issues/2733
https://github.com/Azure/azure-functions-host/issues/9273

and was wondering if the Node worker was in a similar state?

The pricing plan is Y1 using Linux in East US 2, and I am using the latest versions of OpenTelemetry and the various SDKs.