open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Support additional telemetry metadata variation types
@jaydeluca is already working on this.
Since Jul 17, 2026.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
We have some tests with some variability that can't currently be well handled by the existing metadata system - for example runtime metrics. In runtime-metrics we are currently trying to separate the telemetry by runtime variation but using the same mechanism (metadataConfig) as we do for configuration-based variations.
On top of this, we aren't running exhaustive tests for the runtime variations, and are sometimes seeing some churn in the emitted attributes.
See:
- https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19150#discussion_r3549582478
- https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19236/changes#diff-d4a9a82e2e49dddcd092fd546bd57ce2537c32079541611c164a0848fe61e2c1L16084
We should determine if we need some additional when capabilities that can support things like runtime variations on top of standard config variations.
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.