Docs / Record features

The span context

When a step runs inside an active OpenTelemetry span, its receipt records that span's W3C trace id and span id, and the run's manifest records the run's own traceparent. This is the one thing the record keeps about a trace: where the run and its steps ran, so a later reader can line the record up with the spans an app emitted — nothing more.

What is read, and from where

No OpenTelemetry package is required: onetrace reads the active context where it can and the environment otherwise. No network call is made.

What is recorded

A TRACEPARENT that is present but malformed — not a W3C traceparent, or with an all-zero id — is refused and named, never recorded: a broken trace is not written into the record.

What this does not claim