Sending traces to a backend
onetrace export otel writes a run as one OpenTelemetry trace in OTLP/JSON. It makes no network calls and needs no OpenTelemetry package; sending the file is your step.
A trace is a view of a record, never evidence: whether a run is intact is answered by onetrace-verify reading the record.
An OpenTelemetry Collector's file receiver reads the exported file as written, one OTLP JSON request per line, and its otlp_http exporter sends it on, with the destination's key read from your environment.
The trace holds no input, output, constant or assertion value, no exception's text and no file path.
The manual's section 18.1, from onetrace 0.9.0, gives the Collector's configuration in full and works it for LangSmith, Langfuse and a local Jaeger, each from its own documentation as read on 2026-11-15. The manual's section 18.1, Sending a run to a backend.
A restarted Collector sends every file again: move the files already sent out of the folder before starting it again.
One pipeline is run end to end in onetrace's own tests, through otelcol-contrib v0.164.0 to a recording receiver on loopback; the three destinations are not sent to.
For continuous sending from a runs folder, the console's forwarding comes with console 0.9.