open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Consider removing experimental from configuration properties in 3.0 where it makes sense
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
These configuration properties are good candidates for stable names in 3.0:
otel.instrumentation.common.experimental.controller-telemetry.enabledotel.instrumentation.common.experimental.view-telemetry.enabledotel.instrumentation.experimental.span-suppression-strategyotel.instrumentation.messaging.experimental.headers.includedotel.instrumentation.messaging.experimental.headers.excludedotel.instrumentation.messaging.experimental.receive-telemetry.enabledotel.instrumentation.runtime-telemetry.experimental.jfr-metrics.includedotel.instrumentation.runtime-telemetry.experimental.jfr-metrics.excludedotel.instrumentation.sanitization.url.experimental.sensitive-query-parameters
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
Search the repository for each listed configuration property and inspect the related instrumentation references. Read the linked discussion on receive telemetry before deciding which names are appropriate for 3.0. Done means the selected properties consistently use stable names wherever they are defined or referenced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100