Send traces
Send OpenTelemetry traces to Sazabi over OTLP, where spans are stored as searchable records the agent can correlate with your logs, and confirm they arrive.
Sazabi ingests traces over OTLP and stores them as searchable records the agent can correlate with your logs by trace context. For most setups, export OpenTelemetry traces to your project's OTLP intake. By the end you will have traces arriving and confirmed. Setup takes a few minutes plus a redeploy.
How Sazabi handles traces
Traces arrive over the standard OTLP intake and are stored as records. Because they carry trace context, the agent can line up a trace with the logs emitted during the same request — including browser events when the browser SDK propagates trace context to your backend.
Send OpenTelemetry traces
Get your project's OTLP intake URL. In the dashboard, add the OpenTelemetry source under Settings > Log streams and copy the Intake URL from the source's setup screen — your public key is embedded in it, so you copy the whole URL. An agent can do the same with the CLI: sazabi log-sources create otel --mode connectionless mints a keyed OTLP endpoint and prints its intake URL. See CLI reference for install and auth.
Enable the OpenTelemetry tracing SDK in your app, or configure the OTLP trace exporter on your Collector.
Set the OTLP traces environment. OTEL_EXPORTER_OTLP_TRACES_ENDPOINT is
your OTLP intake URL with the /v1/traces path appended. Use the protobuf
protocol:
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=<your intake URL>/v1/traces
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobufRestart or redeploy so the new configuration takes effect.
For the full source page, see OpenTelemetry.
Query traces in a thread
Traces are stored as records, so you query them the way you query logs: open a thread and ask the agent about a request, or search your logs by trace id to pull the spans and correlated log lines together.
Verify
Confirm a trace reaches your project.
- Configure the trace exporter and redeploy as above.
- Exercise a code path that produces a trace (for example, make a request that flows through instrumented services).
- Search for records from the traced service, or by the trace id if you have it. In the dashboard, open your logs and search; an agent can run
sazabi logs query "<service or trace id>" --last 1hinstead. - You should see span records for that request. Allow a short delay — up to about a minute — for export and ingestion.
If nothing appears, confirm you copied the full intake URL for this project, that the path ends in /v1/traces, and that the exporter uses the http/protobuf protocol.