open-telemetry / open-telemetry/opentelemetry-java-instrumentation

Make semantic convention selection OpenTelemetry instance-scoped

Open
#20,135 0 comments 0 reactions 1 assignee View on GitHub

@trask is already working on this.

Since Sep 13, 2026.

enhancement needs triage
Dominant language
Java
Stars
2.6k
Forks
1.2k
Avg merge
2d 18h
Merged PRs (30d)
228

Description

Is your feature request related to a problem? Please describe.

SemconvStability resolves database, messaging, RPC, code, and service-peer modes once from GlobalOpenTelemetry. Instrumentation built with a different ExtendedOpenTelemetry instance can therefore ignore that instance's declarative semconv configuration.

Describe the solution you'd like

Resolve semconv mode from the supplied OpenTelemetry instance and apply the result consistently to attribute extraction, span and metric names, metric units and keys, and schema URLs.

Describe alternatives you've considered

Keeping global selection preserves internal consistency but does not support instance-scoped declarative configuration. Updating schema URLs alone can mislabel telemetry whose attributes still use the global selection.

Additional context

Identified while reviewing #20127.

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.