Rootprint accepts logs two ways:Documentation Index
Fetch the complete documentation index at: https://docs.rootprint.io/llms.txt
Use this file to discover all available pages before exploring further.
- OTLP HTTP — the OpenTelemetry Protocol. Use this with any OTEL SDK, the OTEL Collector, or a sidecar that speaks OTLP. Records land in your OTEL logs index (
otel-logs-v0_9by default). - Rootprint NDJSON gateway — an authenticated HTTP endpoint that forwards NDJSON straight to a Quickwit index. Use this when you control the wire format and want to write to a custom-schema index.
Pick a path
| If you have… | Use |
|---|---|
| An app in Python, Node.js, Go, Java, or .NET | The matching language page (OTLP SDK) |
| Container logs on a Linux host | Docker (OTEL Collector) |
| Logs already on disk on a Linux host | Fluent Bit or Vector |
| Existing pipeline that emits your own schema | HTTP (NDJSON gateway) |
| Something else that speaks OTLP | OTLP reference |
Integrations
Languages
Python
Node.js
Go
Platforms
Docker
Log Agents
Fluent Bit
Vector
Other
HTTP (NDJSON gateway)
Before you start
Every path requires an ingest API key. API keys are created in Settings → API keys and are scoped to a single index — one key, one index. Pick the index you want to write to, create an ingest API key for it, and keep the value ready for the integration page you follow.The built-in
otel-logs-v0_9 index is created on first boot and is ready for OTLP traffic with no
extra configuration. See Indexes for its schema.