semconv.com

Runtimes and processes

as of v1.44.0

Processes, threads, language runtimes and the code that raised the telemetry.

process 38aspnetcore 23pprof 11code 10jvm 8go 4v8js 3thread 2cpython 1dotnet 1nodejs 1profile 1

attributes
103
metrics
126
signals
10
stable
20
deprecated
9

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.

Spans 7

Entities 3

Metrics 126

Specification

Requirements that name this domain 17

  • To avoid sending any name/value pairs to an untrusted process, the Baggage API MUST provide a way to remove all baggage entries from a context.

  • Other common processing scenarios SHOULD be first considered for implementation out-of-process in OpenTelemetry Collector.

  • SHOULDForceFlushStable

    ForceFlush SHOULD only be called in cases where it is absolutely necessary, such as when using some FaaS providers that may suspend the process after an invocation, but before the LogRecordProcessor exports the emitted LogRecords.

  • SHOULDForceFlushStable

    ForceFlush SHOULD only be called in cases where it is absolutely necessary, such as when using some FaaS providers that may suspend the process after an invocation, but before the exporter exports the ReadlableLogRecords.

  • In case of any error, e.g. failure during the decoding process, the entire environment variable value SHOULD be discarded and an error SHOULD be reported following the Error Handling principles.

  • SHOULDForceFlush()Stable

    ForceFlush SHOULD only be called in cases where it is absolutely necessary, such as when using some FaaS providers that may suspend the process after an invocation, but before the SpanProcessor exports the completed spans.

  • SHOULD`ForceFlush()`Stable

    ForceFlush SHOULD only be called in cases where it is absolutely necessary, such as when using some FaaS providers that may suspend the process after an invocation, but before the exporter exports the completed spans.

  • MAYPropagationStable

    Baggage MAY be propagated across process boundaries or across any arbitrary boundaries (process, $OTHERBOUNDARY1, $OTHERBOUNDARY2, etc) for various reasons.

All 17 matching requirements

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

Attributes 103

process38 attributes

aspnetcore23 attributes

pprof11 attributes

code10 attributes

  • code.column
    Deprecated→ code.column.numberDeprecated, use code.column.number
  • code.column.number
    StableThe column number in code.file.path best representing the operation. It SHOULD point within the code unit named in code.function.name. This attribute MUST NOT b
  • code.file.path
    StableThe source code filename that identifies the code unit as uniquely as possible (preferably an absolute file path). This attribute MUST NOT be used on the Profil
  • code.filepath
    Deprecated→ code.file.pathDeprecated, use code.file.path instead
  • code.function
    DeprecatedDeprecated, use code.function.name instead
  • code.function.name
    StableThe method or function fully-qualified name without arguments. The value should fit the natural representation of the language runtime, which is also likely the
  • code.line.number
    StableThe line number in code.file.path best representing the operation. It SHOULD point within the code unit named in code.function.name. This attribute MUST NOT be
  • code.lineno
    Deprecated→ code.line.numberDeprecated, use code.line.number instead
  • code.namespace
    DeprecatedDeprecated, namespace is now included into code.function.name
  • code.stacktrace
    StableA stacktrace as a string in the natural representation for the language runtime. The representation is identical to exception.stacktrace. This attribute MUST NO

jvm8 attributes

go4 attributes

v8js3 attributes

thread2 attributes

  • thread.id
    DevelopmentCurrent "managed" thread ID (as opposed to OS thread ID).
  • thread.name
    DevelopmentCurrent thread name.

cpython1 attributes

dotnet1 attributes

nodejs1 attributes

profile1 attributes

Recent changes

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

  • stabilitymetricprocess.context_switchesPromoted to release_candidate.
  • stabilitymetricprocess.cpu.timePromoted to release_candidate.
  • stabilitymetricprocess.cpu.utilizationPromoted to release_candidate.
  • stabilitymetricprocess.disk.ioPromoted to release_candidate.
  • stabilitymetricprocess.memory.usagePromoted to release_candidate.
  • stabilitymetricprocess.memory.virtualPromoted to release_candidate.
  • stabilitymetricprocess.network.ioPromoted to release_candidate.
  • stabilitymetricprocess.paging.faultsPromoted to release_candidate.
  • stabilitymetricprocess.thread.countPromoted to release_candidate.
  • stabilitymetricprocess.unix.file_descriptor.countPromoted to release_candidate.

37 more in the full release history

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