open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Promote code semantic conventions from instrumentation-api-incubator to instrumentation-api
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
Move CodeAttributesGetter, CodeAttributesExtractor, and CodeSpanNameExtractor from io.opentelemetry.instrumentation.api.incubator.semconv.code in instrumentation-api-incubator to io.opentelemetry.instrumentation.api.semconv.code in instrumentation-api.
This follows the HTTP promotion in 2.0: remove old semconv support first (#9968), then move the classes without leaving deprecated shims behind (#9977).
Dropping the emitOldCodeSemconv() branch from CodeAttributesExtractor changes emitted telemetry, which is why this waits for 3.0.
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 CodeAttributesGetter, CodeAttributesExtractor, and CodeSpanNameExtractor in instrumentation-api-incubator and reviewing the earlier HTTP promotion references, #9968 and #9977. Move the classes into the instrumentation-api package, remove the old semconv support without deprecated shims, and run the affected module tests and build to verify the migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability-sre
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100