Update usage of semantic conventions to new exported strings

[JamieDanielson]

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

• update the dependency for @opentelemetry/semantic-conventions to "^1.22.0"
• update the imported semantic convention to match the new version, i.e. HTTP_ROUTE becomes SEMATTRS_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 refactor(shim-opentracing): Use tree-shakeable string constants for semconv #4746
• @opentelemetry/sdk-trace-web refactor(sdk-trace-web): Use tree-shakeable string constants for semconv #4747
• @opentelemetry/sdk-trace-node refactor(sdk-trace-node): Use tree-shakeable string constants for semconv #4748
• @opentelemetry/sdk-trace-base refactor(sdk-trace-base): Use tree-shakeable string constants for semconv #4749
• @opentelemetry/resources chore(resources): update deprecated semconv to use exported strings #4755
• @opentelemetry/exporter-zipkin chore(exporters): updated deprecated semconv to use exported strings #4756
• @opentelemetry/exporter-jaeger chore(exporters): updated deprecated semconv to use exported strings #4756
• @opentelemetry/core refactor(core): Use (tree-shakeable) string constants for semconv #4739
• @opentelemetry/sdk-node refactor(sdk-node): Use tree-shakeable string constants for semconv #4767
• @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 chore(exporters): updated deprecated semconv to use exported strings #4756
• @opentelemetry/opentelemetry-browser-detector docs(opentelemetry-browser-detector): Use tree-shakeable string constants for semconv in Readme #4768
• examples/basic-tracer-node refactor(examples/basic-tracer-node): use new exported string constants for semconv #4759
• examples/esm-http-ts refactor(examples/esm-http-ts): use new exported string constants for semconv #4758
• examples/grpc-js refactor(examples/grpc-js): use new exported string constants for semconv #4760
• examples/http refactor(examples/http): use new exported string constants for semconv #4750
• examples/https refactor(examples/https): use new exported string constants for semconv #4753
• examples/opentelemetry-web refactor(examples/opentelemetry-web): use new exported string constants for semconv #4764
• examples/opentracing-shim refactor(examples/opentracing-shim): use new exported string constants for semconv #4761
• examples/otlp-exporter-node refactor(examples/otlp-exporter-node): use new exported string constants for semconv #4762
• examples/opencensus-shim refactor(experimental/examples/opencensus-shim): use new exported string constants for semconv #4763

[JamieDanielson]

I am working on http package

[pahiz]

PR for instrumentation-fetch #4632

[Prashansa-K]

@JamieDanielson Can I also contribute in this issue? I can start working on this package - @opentelemetry/instrumentation-xml-http-request if no one has picked this up yet.

[Prashansa-K]

Created a PR for instrumentation-xhr here: #4681

[JohannesHuster]

I am working on core package.

[JohannesHuster]

I'm working on

• @opentelemetry/shim-opentracing
• @opentelemetry/sdk-trace-web
• @opentelemetry/sdk-trace-node
• @opentelemetry/sdk-trace-base

[Zen-cronic]

hey, i'm working on:

• examples/basic-tracer-node
• examples/esm-http-ts
• examples/grpc-js
• examples/http
• examples/https
• examples/opencensus-shim
• examples/opentracing-shim
• examples/otlp-exporter-node

[Zen-cronic]

@JamieDanielson hey, i found that in each example in the examples/opentelemetry-web directory, there's no usage of @opentelemetry/semantic-conventions. But it's installed as a dep in package.json. And it's already been updated to 1.24.1. So i think the issue list can do without it!

[JamieDanielson]

@JamieDanielson hey, i found that in each example in the examples/opentelemetry-web directory, there's no usage of @opentelemetry/semantic-conventions. But it's installed as a dep in package.json. And it's already been updated to 1.24.1. So i think the issue list can do without it!

It looks like they are being used for the service name, as seen here in esm-http-ts example. We'll need to replace SemanticResourceAttributes.SERVICE_NAME with the SEMRESATTRS_SERVICE_NAME constant instead. If it helps, take a look at this PR in the js-contrib repo for guidance.

[Zen-cronic]

@JamieDanielson hey, i found that in each example in the examples/opentelemetry-web directory, there's no usage of @opentelemetry/semantic-conventions. But it's installed as a dep in package.json. And it's already been updated to 1.24.1. So i think the issue list can do without it!

It looks like they are being used for the service name, as seen here in esm-http-ts example. We'll need to replace SemanticResourceAttributes.SERVICE_NAME with the SEMRESATTRS_SERVICE_NAME constant instead. If it helps, take a look at this PR in the js-contrib repo for guidance.

Hey, thanks for the pointers. But i mean that none of the example in the opentelemetry-web imports @opentelemetry/semantic-conventions. For e.g., the code in the fetch example inside opentelemetry-web doesn't use the semantic-conventions package. I hope this clarifies it.

[JamieDanielson]

Hey, thanks for the pointers. But i mean that none of the example in the opentelemetry-web imports @opentelemetry/semantic-conventions. For e.g., the code in the fetch example inside opentelemetry-web doesn't use the semantic-conventions package. I hope this clarifies it.

Oh! I see what you mean now, sorry I read too fast earlier 😅 . It looks like service names were removed inadvertently during an update and migration of this example a few years back actually, so I see we have two options: either remove the semantic conventions package from the package.json since it's not being used, or add the resource and service name for these to match the other examples. I'm leaning toward the second option, what do you think?

[Zen-cronic]

Oh! I see what you mean now, sorry I read too fast earlier 😅 . It looks like service names were removed inadvertently during an update and migration of this example a few years back actually, so I see we have two options: either remove the semantic conventions package from the package.json since it's not being used, or add the resource and service name for these to match the other examples. I'm leaning toward the second option, what do you think?

No problem at all! Oh i see. Removing the unused dep would be straightforward, but i think we should aim for consistency with the other examples. So, i'm down with the 2nd option too.

[JamieDanielson]

I am going to update the remaining items in the resources package

[JamieDanielson]

Also going to update exporter-zipkin, exporter-jaeger, and exporter-prometheus

[Zen-cronic]

i'm on the examples/opentelemetry-web now

[JohannesHuster]

I'm working on sdk-node and opentelemetry-browser-detector.