open-telemetry / open-telemetry/opentelemetry-python
Django gunicorn auto instrumentation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
Currently, Django autoinstrumentation supports flask and uWSGI servers.
However, when running django app using gunicorn server, the autoinstrumentation does not work.
This is the command I am trying to run.
opentelemetry-instrument --trace-exporter zipkin_json python3.8 gunicorn ${DJANGO_WSGI_MODULE}:application --name ${NAME} --bind=127.0.0.1:80 --preload
The app starts fine, but doesn't report any traces to zipkin.
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 reported command with Django, Gunicorn, and the Zipkin exporter, then compare the existing Flask and uWSGI autoinstrumentation paths. Done means the same Gunicorn invocation starts successfully and reports Django traces to Zipkin; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100