OpenTelemetry

Send OTLP HTTP traces into Mydle. Spans that were not observed are never fabricated.

OTLP ingest#

Point your OTLP HTTP exporter at POST /api/traces/v1/otlp. This is the documented customer ingest path for traces. OTLP/HTTP protobuf (recommended) and JSON are accepted, optionally gzip; OTLP/gRPC is not supported. Setup, limits and retry behaviour: OTLP Ingestion.

Auth#

Authenticate with a tracing source token (tt_…). Create tokens from the tracing connect flow. See API Keys.

Correlation#

Prefer W3C traceparent and shared trace_id / session IDs so logs and browser events can join. Query helpers: GET /api/app/traces/search, GET /api/app/correlation, GET /api/v1/traces.

Product guides#

Limitations

OTLP metrics / logs pipelines are not a first-class customer surface yet.
Spans count toward the workspace’s monthly span and span-data allowance (Free 50,000, Pro 1,000,000).