search

open-telemetry / semantic-conventions

Defines standards for generating consistent, accessible telemetry across a variety of domains
Apache License 2.0
269 stars 174 forks source link

Document how consumers should identify browser telemetry #1443

Open martinkuba opened 3 months ago

martinkuba commented 3 months ago

Related to https://github.com/open-telemetry/opentelemetry-specification/issues/2466

If consumers of telemetry wanted to distinguish browser telemetry from other types, they can use the value of process.runtime.name resource attribute (the value is always "browser" per semantic conventions).

I would like to document this somewhere. Please advise where is the best place to do so.

danielgblanco commented 3 months ago

@open-telemetry/docs-maintainers do we have a specific section that you'd recommend for something like this? Personally, I think semconv "is" the place for it, but I can understand how it may be a little bit buried in detail for the end-user.

The best place I can think of would be something linking https://opentelemetry.io/docs/languages/js/getting-started/browser/ to the semconv docs.

svrnm commented 3 months ago

Yeah, this belongs into SemConv. Maybe here: https://opentelemetry.io/docs/specs/semconv/resource/ -- this page already has some notes on SDK defaults?