Menu

Product hub

Controlled BetaLivePreview ContractVerification RequiredFuture

LogDB

LogDB documentation starts with current local OTLP logs and traces ingestion, WAL-backed segment publication, segment-bundle storage, and authenticated query, then keeps S3 publication, replay APIs, BYOC, scale, and GA language behind explicit evidence gates.

Current availability

Private Beta. Public beta is scheduled for .

Primary Evaluation Path

  1. Ingest telemetryStart with endpoint JSON, OTLP HTTP/protobuf, OTLP JSON compatibility, or optional gRPC logs and traces.
  2. Publish segmentsKeep the local WAL, segment publication, manifest, and Parquet bundle model close to the claim.
  3. Query retained recordsUse POST /v1/query with tenant auth, exact identifiers, time filters, pagination, and deadlines.
  4. Hold gated claimsKeep replay routes, S3 publication, BYOC deployment, performance, and GA claims in review-bound language.

Surface Status

OTLP logs and traces ingest

Live

Lead with health, endpoint JSON ingestion, native OTLP HTTP/protobuf logs and traces, OTLP HTTP JSON compatibility routes, optional OTLP/gRPC, and the authenticated query route.

Evidence: Fact sheet: README.md and product-plan.md

WAL-backed publication

Verification Required

Describe endpoint and OTLP requests as passing through the local live WAL before segment publication, while keeping replicated-local mode, recovery, and fault evidence visibly bounded.

Evidence: Fact sheet: live-wal-gateway.md

Segment bundle v1

Live

Use the manifest-controlled bundle model with Parquet data, statistics, exact identifier indexes, retention metadata, and encryption metadata fields.

Evidence: Fact sheet: segment-bundle-v1.md

Query API

Live

Frame POST /v1/query as local segment search by default, with exact identifier filters, dataset and time filters, pagination, deadline behavior, and optional S3 query-read selection.

Evidence: Fact sheet: http-query-api.md

Replay and audit foundations

Preview Contract

Keep replay preview, job, checkpoint, and audit evidence language tied to the local coordinator; public replay routes and external sinks remain future work.

Evidence: Fact sheet: README.md and product-plan.md

BYOC and S3 direction

Verification Required

Treat BYOC packaging and customer-owned S3 as gated direction until approved-bucket publication conformance, shared S3 read evidence, security review, and support paths are attached.

Evidence: Fact sheet: product-plan.md

Route Families

Health and endpoint JSON

GET /health plus POST /v1/endpoint/{activation_id} for canonical JSON telemetry payload ingestion and deterministic record IDs.

Native OTLP HTTP

POST /v1/logs and POST /v1/traces accept OTLP protobuf logs and traces through the tenant-admitted commit path.

OTLP JSON compatibility

POST /v1/otlp/logs and POST /v1/otlp/traces support OpenTelemetry-shaped JSON compatibility batches for local evaluation.

Optional OTLP gRPC

LogsService Export and TraceService Export are enabled when LOGDB_OTLP_GRPC_BIND_ADDRESS is configured.

Query

POST /v1/query searches published local or configured S3 segment bundles with tenant auth, filters, pagination, and stable errors.

Storage and replay foundations

Local segment bundles, WAL recovery evidence, replay coordinator checkpoints, and audit files support bounded follow-up docs.

Boundaries to Keep Visible

Live Is Narrow

Current docs can name local ingest, segment publication, and query behavior, but GA, support, availability, and performance claims need approved evidence.

S3 Read vs Publication

The query route can be configured to read from S3 segment storage; S3-backed publication still needs approved-bucket conformance and operations review.

Replay Foundations

The local coordinator can preview selections, create jobs, persist checkpoints, and append audit evidence, but public replay APIs and external sinks stay future-facing.

Signal Scope

Keep LogDB focused on logs, traces, retained segment search, and replay foundations; do not present it as a metrics, profiles, dashboard, or SIEM replacement.

Safe Next Steps

  • Available now

    Run OTLP ingest and query quickstart

    Send OTLP or JSON compatibility payloads, capture record IDs, query retained records, and see tenant-header requirements.

  • Available now

    Review LogDB evidence

    Use the evidence index before strengthening ingest, query, S3, replay, BYOC, or GA claims.

  • Available: DOCS-033

    Read OTLP and query reference

    Document OTLP HTTP/protobuf, optional gRPC, JSON compatibility routes, custom endpoints, and POST /v1/query.

  • Available: DOCS-034

    Review configuration and BYOC reference

    Separate local bind/data settings, WAL modes, S3 query-read settings, gRPC bind configuration, and AWS BYOC values.

  • Available: DOCS-039

    Compare OTLP and S3 query scope

    Distinguish live ingest, optional gRPC, local query, S3 query reads, metrics/profile exclusions, and future publication work.

  • Available: DOCS-042

    Read known limits

    See what happens for metrics/profile exclusions, S3 query-read boundaries, replay APIs, external sinks, and BYOC claims.

  • Available: DOCS-052

    Use operator runbooks

    Check OTLP admission failures, WAL issues, segment bundles, query troubleshooting, S3 query-read boundaries, BYOC preflight, and support evidence.

  • Available: DOCS-060

    Use OpenTelemetry Collector examples

    Run collector and curl examples with required tenant/auth headers, retained-record query checks, and local-development policy warnings.