open-telemetry / open-telemetry/opentelemetry-python-contrib
Add backend information in celery instrumentation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
What problem do you want to solve?
While using celery instrumentation, the instrumentation does not provide information about which backend is begin used.
Describe the solution you'd like
-
Check if it is feasible to add the instrumentation to figure out underlying backend (rabbitMQ, MongoDB, redis, etc)
-
Add the required instrumentation
-
This should be added as
messaging.systemattribute in Celery span attributes
Describe alternatives you've considered
No response
Additional Context
No response
Would you like to implement a fix?
None
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 locating the Celery instrumentation and its span attribute handling. Determine whether the underlying RabbitMQ, MongoDB, or Redis backend can be identified, then verify that the selected backend is exposed as the messaging.system attribute on Celery spans.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, python, rabbitmq, redis
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100