open-telemetry / open-telemetry/opentelemetry-python-contrib
Make sure confluent-kafka 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
Locate the confluent-kafka instrumentation entry point and review how its telemetry is named against the applicable semantic conventions. Confirm the required conventions before changing anything; done means the instrumentation follows those conventions and its existing checks still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, python
- Domain
- observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100