open-telemetry / open-telemetry/opentelemetry-python-contrib
Implement tracing for remaining Celery Task signals
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
There is no implementation of tracing for the following task signals in celery
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 reading the existing Celery instrumentation and the linked Celery signal documentation for task_internal_error, task_received, task_revoked, task_unknown, and task_rejected. Trace how currently supported task signals are handled, then verify that tracing covers all five remaining signals with appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100