open-telemetry / open-telemetry/opentelemetry-python-contrib
Make sure celery instrumentation follows semantic conventions
Open
Nobody has claimed this yet.
good first issue
help wanted
instrumentation
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
This issue has no description.
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 entry point in this repository and reviewing its current emitted telemetry against the applicable semantic conventions. The issue provides no files, tests, or detailed acceptance criteria, so confirm the expected convention changes and validation approach before beginning; done means the instrumentation conforms and its tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100