open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Add support for `service.peer.name`
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
peer.service was renamed to service.peer.name in https://github.com/open-telemetry/semantic-conventions/pull/3097 and should hopefully stabilize soon.
TODO
- https://github.com/open-telemetry/semantic-conventions/pull/3352
- Apply throughout codebase
- #16046
- #16058
- #16061
- #16059
- #16066
- #16078
- #16108
- #16146
- Update incubating APIs to reflect new name
- #16071
- Update internal terminology usage to reflect new name
- #16149
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 semantic-conventions PR 3352 and the completed checklist items in this issue, including #16046 and #16071. Determine whether any Java instrumentation support remains after that external change; done means the renamed service.peer.name attribute is supported throughout the repository and the issue checklist can be completed.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100