-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracing is broken when AspNetCore integration is used #2875
Comments
Are you using AspNetCore integration here? |
Yes, it's configured in |
This is a known issue we are working on for AspNetCore integration. We have AspNetCore and Functions pipelines both creating their own activity to track this work and those two pipelines are disjointed, causing the correlation issue. |
Awesome, feel free to close if it's a duplicate |
I am not sure if we have a different issue tracking this. I will leave this open until I find that. |
@jviau, Were you able to find the issue that we can track to keep updated about when there is a fix for this? |
Description
I configure ASP.NET Core integration along with OTel in the following way
and enable host telemetry with
In my function code I create another activity
What I get:
I.e.
GET
- incoming HTTP request to hostGET
- outgoing HTTP request from host to workerTestFuncs GET api/Function1
- incoming request on worker tracked by ASP.NET Core and OTel instrumentation on the workerTHIS IS A TEST
generated withinFunction1
execution. It's a child of the incoming request to host - this is the problemWhat I expect
GET
- incoming HTTP request to hostGET
- outgoing HTTP request from host to workerTestFuncs GET api/Function1
- incoming request on worker tracked by ASP.NET Core and OTel instrumentation on the workerTHIS IS A TEST
generated withinFunction1
execution. It's a child of the incoming request to workerSteps to reproduce
docker run --rm -p 18888:18888 -p 4317:18889 -p 4318:18890 --name aspire-dashboard mcr.microsoft.com/dotnet/nightly/aspire-dashboard:latest
Related to #2733
The text was updated successfully, but these errors were encountered: