You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 as well, but no luck. I also tried adding the AlwaysOnSampler indicated in this issue, but that also didn't seem to help.
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.
The text was updated successfully, but these errors were encountered:
KiithNabaal
changed the title
OpenTelemetry integration with Node.js Function Apps
OpenTelemetry integration with Node.js Function Apps, seems like spans are missing
Oct 24, 2024
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 as well, but no luck. I also tried adding the AlwaysOnSampler indicated in this issue, but that also didn't seem to help.
I read some other Github issues here:
Azure/azure-functions-dotnet-worker#2543
Azure/azure-functions-dotnet-worker#2733
Azure/azure-functions-host#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.
The text was updated successfully, but these errors were encountered: