On a terminal you get readable text. Anywhere else, such as a container whose output goes to a log shipper, you get one JSON object per line, with each field as a key of its own. Lines inside a span carry its fields and its trace id, so you can find everything one request did.
Rust code already records spans, logs and metrics with tracing and metrics. oxtel turns them into log lines, OTLP for collectors and backends, and Prometheus scrapes. There’s no second API to learn, and no bridge between two.
Nothing is sent until you say so
With no settings, you get log lines and nothing else. Set OTEL_EXPORTER_OTLP_ENDPOINT and traces, metrics and logs go there, with no rebuild.
It tells you what it did
When it starts, one line says where each kind of telemetry goes. If sending fails, it says so, and what to check.
Built to the standards
The OpenTelemetry settings, protocol and naming conventions. CI checks the output against a real OpenTelemetry Collector and Prometheus’s own checker.