open-telemetry / open-telemetry/opentelemetry-java-instrumentation
More extensions support
@steverao is already working on this.
Since Aug 13, 2025.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
Higher Priority for extensions
-
Support distinguishing between different instrumenters within the same instrumentation.
-
Current Status: Currently, customization decisions are based on the instrumentation name, which fails to distinguish between different instrumenters under the same instrumentation (e.g., armeria client and server). Related https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/13917
-
Proposed Solution: Provide a dynamic check mechanism to expose the original span name and kind, Or we could use the span suppression keys (the ones that we get from the extractors) to expose what kind of instrumenter we are dealing with.
Medium priority for extensions
- Support modifying span kind.
- Requirement: The current customization capabilities do not cover span kind modification. This customization scenario needs to be evaluated and supported.
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.
Assessment
This issue has not been assessed yet.