open-telemetry / open-telemetry/opentelemetry-python-contrib
opentelemetry-instrumentation-asgi is extremely noisy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
Describe your environment Potentially relevant python package versions:
fastapi==0.95.2
opentelemetry-distro==0.43b0
opentelemetry-exporter-otlp==1.22.0
opentelemetry-instrumentation-logging==0.43b0
opentelemetry-instrumentation-urllib==0.43b0
opentelemetry-instrumentation-wsgi==0.43b0
opentelemetry-instrumentation-aiohttp-client==0.43b0
opentelemetry-instrumentation-fastapi==0.43b0
opentelemetry-instrumentation-tornado==0.43b0
opentelemetry-instrumentation-urllib3==0.43b0
Steps to reproduce
Automatically instrument a FastAPI application
What is the expected behaviour?
The start of the trace, and possibly one span representing the time to receive the post content.
What is the actual behaviour?
A large number of tiny spans are created.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with an automatically instrumented FastAPI application using the listed package versions, and inspect the spans created while receiving POST content. Done means the instrumentation produces the expected trace start and at most one span for receiving the post content instead of many tiny spans.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python
- Domain
- api, backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100