OTLP reference

Rootprint accepts OpenTelemetry logs over OTLP HTTP and authenticates them with an ingest API key.

Endpoint

POST https://<your-rootprint>/v1/logs

Authentication

Authorization: Bearer <your-ingest-api-key>

In OTEL_EXPORTER_OTLP_LOGS_HEADERS, write the space after Bearer as %20. See Environment variables.

Supported content types

Rootprint accepts application/x-protobuf only. Any other Content-Type returns 415. In Node.js, use @opentelemetry/exporter-logs-otlp-proto. @opentelemetry/exporter-logs-otlp-http sends JSON. Both packages export the same OTLPLogExporter API.

Encoding

Content-Encoding: gzip / x-gzip, zstd, deflate / x-deflate, and identity (or no header) for uncompressed. Any other value is rejected.

Response codes

Retry 429 and 503 after the Retry-After delay.

Status	Meaning
`200`	Accepted. The body carries `partial_success` when some records were rejected.
`400`	Empty request body, or the payload was rejected.
`401`	Missing `Authorization: Bearer` header.
`403`	Invalid or unknown ingest API key.
`413`	Payload too large, usually at a reverse proxy. Lower the agent’s batch size (`batch.max_bytes` in Vector, `send_batch_max_size` on the Collector’s `batch` processor, `batch_size` on Fluent Bit’s `opentelemetry` output, default 1000 records) or raise the proxy’s body limit.
`415`	`Content-Type` is not `application/x-protobuf`.
`429`	Quickwit is rate-limiting ingestion. `Retry-After` gives the wait in seconds (default 5).
`503`	Quickwit is unreachable or returned an error, or the request ran past `INGEST_PROXY_TIMEOUT_MS` (120 seconds by default). Keep that timeout below your agent’s request timeout, so the agent gets this retryable `503` instead of timing out. `Retry-After: 5`.

Environment variables

Variable	Value
`OTEL_SERVICE_NAME`	Your service name (lands in `service_name`).
`OTEL_EXPORTER_OTLP_LOGS_ENDPOINT`	`https://<your-rootprint>/v1/logs`
`OTEL_EXPORTER_OTLP_LOGS_HEADERS`	`Authorization=Bearer%20<your-ingest-api-key>`
`OTEL_EXPORTER_OTLP_LOGS_PROTOCOL`	`http/protobuf`. Set it if your SDK defaults to gRPC or JSON. The exporters on the language pages already send protobuf.

Index target

The ingest API key sets the target index, not the SDK. A key scoped to another index writes there without an error. To write to a different index, create an ingest API key scoped to that index in Settings → API keys. See Manage indexes.

OTLP logs only land in an index with the OpenTelemetry logs schema, such as the bundled otel-logs-v0_9. Sent to any other index, they get a 200 and are discarded, so nothing arrives and no error surfaces. Scope OTLP ingest keys to an OpenTelemetry logs index, and send custom-schema data to the NDJSON gateway instead.

Spans go to POST /v1/traces with the same key and always land in the span store, not the key’s index. See Traces overview.

Get Started

Send Logs

Traces

Search Logs

Manage Rootprint

Endpoint

Authentication

Supported content types

Encoding

Response codes

Environment variables

Index target

​Endpoint

​Authentication

​Supported content types

​Encoding

​Response codes

​Environment variables

​Index target

​Related

Endpoint

Authentication

Supported content types

Encoding

Response codes

Environment variables

Index target

Related