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
When using the autoinstrumentation with 0.50b0 all of the incoming requests to my FastAPI application get the same trace id when incoming requests do not have trace headers.
I expect to see two different trace_id's in the spans exported to the console. I get that result when using 0.49b0 and 0.48b0 for the opentelemetry-distro.
Actual Result
I see the same value for trace_id in the spans.
Additional context
When stopping the app I see another span for "uvicorn" with a duration of the start/end times aligning with when I started and stopped the app and a span_id equal to the parent_id of the spans for "GET /".
Describe your environment
OS: Alpine (container) and MacOS arm64 (local)
Python version: Python 3.11.9
Package version: 0.50b0
What happened?
When using the autoinstrumentation with 0.50b0 all of the incoming requests to my FastAPI application get the same trace id when incoming requests do not have trace headers.
Steps to Reproduce
requirements.txt
main.py
run app
Expected Result
curl localhost:8000 && curl localhost:8000
I expect to see two different trace_id's in the spans exported to the console. I get that result when using 0.49b0 and 0.48b0 for the opentelemetry-distro.
Actual Result
I see the same value for trace_id in the spans.
Additional context
When stopping the app I see another span for "uvicorn" with a duration of the start/end times aligning with when I started and stopped the app and a span_id equal to the parent_id of the spans for "GET /".
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: