open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Bump RPC instrumentation to the latest semconv in 3.0, even if RPC semconv isn't stable yet
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 214
Description
(similar to messaging)
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 RPC instrumentation and compare its semantic-convention handling with the similar messaging work referenced in the issue. Determine the latest RPC semconv expected for the 3.0 line, then verify the instrumentation and its relevant tests use that version even while the RPC semconv remains unstable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100