Update usage of semantic conventions to new exported strings #4567
Labels
good first issue
Good for newcomers
needs:code-contribution
This feature/bug is ready to implement
type:feature-tracking
A feature with sub-issues that need to be addressed
up-for-grabs
Good for taking. Extra help will be provided by maintainers
Same as open-telemetry/opentelemetry-js-contrib#2025 for core repo.
This issue is intended to track the necessary change of updating each package to use the new exports for semantic conventions that were added in #4298 and now available in v1.22.0.
Each package will need to
@opentelemetry/semantic-conventions
to"^1.22.0"
HTTP_ROUTE
becomesSEMATTRS_HTTP_ROUTE
Please limit PRs to a single package in order to make them quickly and easily reviewable.
If you are working on one of the below packages, please comment so others know the issue is being worked on.
@opentelemetry/shim-opentracing
@opentelemetry/sdk-trace-web
@opentelemetry/sdk-trace-node
@opentelemetry/sdk-trace-base
@opentelemetry/resources
@opentelemetry/exporter-zipkin
@opentelemetry/exporter-jaeger
@opentelemetry/core
@opentelemetry/sdk-node
@opentelemetry/instrumentation-xml-http-request
refactor(instrumentation-xhr): use exported strings for semantic attr… #4681@opentelemetry/instrumentation-http
refactor(instr-http): use exported strings for semconv #4573@opentelemetry/instrumentation-grpc
refactor(instr-grpc): move to use SEMATTRS #4633@opentelemetry/instrumentation-fetch
refactor(instr-fetch): move fetch to use SEMATRR #4632@opentelemetry/exporter-prometheus
@opentelemetry/opentelemetry-browser-detector
The text was updated successfully, but these errors were encountered: