Closed as not planned
Closed as not planned
Description
What version of OpenTelemetry are you using?
"dependencies": {
"@opentelemetry/auto-instrumentations-node": "^0.55.0",
"@opentelemetry/exporter-trace-otlp-proto": "^0.57.0",
"@opentelemetry/sdk-node": "^0.57.0",
"@opentelemetry/sdk-trace-base": "^1.30.0"
}
What version of Node are you using?
20.18
What did you do?
Repo to reproduce with steps in the README: https://github.com/drewcorlin1/fastify-otel-bug-example
What did you expect to see?
The route handler as a child span of the GET /example
from @opentelemetry/instrumentation-http
(and thus, jaeger correctly identifying the critical path of the request)
What did you see instead?
The route handler has a child span of the first middleware span middleware - fastify -> @fastify/request-context
from @opentelemetry/instrumentation-fastify
(and thus jaeger incorrectly identifying the critical path of my trace)
Additional context
Screenshot of what I'm seeing and full JSON of the trace downloaded from jaeger attached