semconv.com

Telemetry and the SDK

as of v1.44.0

Telemetry describing itself: the service and SDK that emitted it, and the log and event plumbing.

otel 12log 7service 7telemetry 5event 1opentracing 1state 1

attributes
34
metrics
23
signals
6
stable
14
deprecated
4

Signals

What this domain emits, and the attributes each one carries, most strongly required first. An attribute marked * is required on that signal; * is conditionally required.

Entities 6

Metrics 23

Specification

Requirements that name this domain 43

  • MUSTSchema URLStable

    The fetcher MUST follow the HTTP standard and honour the redirect response and fetch the file from the redirected URL.

  • MUSTSchema URLStable

    The schema file that corresponds to the new version MUST be retrievable at a new URL.

  • MUSTSpan ExporterStable

    Each implementation MUST document the concurrency characteristics the SDK requires of the exporter.

  • This tuple SHOULD uniquely identify the logical unit of software that emits the telemetry.

  • The instrumentation scope's name SHOULD be specified to identify the InstrumentationScope name.

  • The instrumentation scope's optional Schema URL SHOULD identify the Telemetry Schema that the instrumentation's emitted telemetry conforms to.

  • Exporters to formats that don't have a concept that is equivalent to the Scope SHOULD record the attributes at the most suitable place in their corresponding format, typically at the Span, Metric or LogRecord equivalent.

  • SHOULD NOTExporter SelectionStable

    It SHOULD NOT be supported by new implementations.

All 43 matching requirements

On the wire, this lands in metrics/v1/metrics, resource/v1/resource. Field-by-field definitions are under OTLP.

Attributes 34

otel12 attributes

log7 attributes

service7 attributes

  • service.criticality
    AlphaThe operational criticality of the service.
  • service.instance.id
    StableThe string ID of the service instance.
  • service.name
    StableLogical name of the service.
  • service.namespace
    StableA namespace for service.name.
  • service.peer.name
    DevelopmentLogical name of the service on the other side of the connection. SHOULD be equal to the actual service.name resource attribute of the remote service if any.
  • service.peer.namespace
    DevelopmentLogical namespace of the service on the other side of the connection. SHOULD be equal to the actual service.namespace resource attribute of the remote service i
  • service.version
    StableThe version string of the service component. The format is not defined by these conventions.

telemetry5 attributes

event1 attributes

  • event.name
    DeprecatedIdentifies the class / type of event.

opentracing1 attributes

state1 attributes

Recent changes

Breaking and notable changes to this domain across the last 6 semantic-conventions releases.

Topics are this site's grouping of upstream namespaces, not a structure the OpenTelemetry project publishes. JSON · All domains