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
What is the expected behavior?
If the tracing already propagates with the Jaeger header(example from Traefik as the reverse proxy and with tracing enabled), we should still have the trace propagated successfully in FastAPI Instrumentation.
What is the actual behavior?
now even with default swagger pages, it will have exceptions on opening. ofc, I have reverse proxy both API and Documents.
any request coming with the Jaeger header will have issues as below
any request that does not have a previous jaeger header will still be fine (because the asgi getter will have no issue with processing empty headers)
Describe your environment
Steps to reproduce
example Traefik config
What is the expected behavior?
If the tracing already propagates with the Jaeger header(example from Traefik as the reverse proxy and with tracing enabled), we should still have the trace propagated successfully in FastAPI Instrumentation.
What is the actual behavior?
now even with default swagger pages, it will have exceptions on opening. ofc, I have reverse proxy both API and Documents.
Additional context
I believe the issue from this specific line https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/instrumentation/opentelemetry-instrumentation-asgi/src/opentelemetry/instrumentation/asgi/__init__.py#L263, and I can confirm the older version 0.34b0 with this impl https://github.com/open-telemetry/opentelemetry-python-contrib/blob/v0.34b0/instrumentation/opentelemetry-instrumentation-asgi/src/opentelemetry/instrumentation/asgi/__init__.py#L217 have no issue.
The text was updated successfully, but these errors were encountered: