Menu

Guides

Verification Required

LogDB Guides

LogDB guides collect collector examples and decision support for local OTLP logs/traces ingest, retained-record query, tenant policy, and review-bound S3 or BYOC claims.

Current availability

Private Beta. Public beta is scheduled for .

Guide Scope

Start here when a workflow is larger than a reference snippet but not a first-success quickstart. The initial LogDB guide publishes OpenTelemetry Collector and curl examples as tested source-backed examples while keeping local policy, external process, and S3 boundaries under reviewer acceptance.

Guide Pages

  • Available: DOCS-060

    LogDB OpenTelemetry Collector examples

    Tested collector config, smoke-runner commands, and curl examples for logs/traces ingest, retained-record query, tenant headers, and local policy boundaries.

  • Available: DOCS-024

    LogDB OTLP ingest and query quickstart

    Use the local curl workflow when readers need a copy/paste first-success path before adapting collector configuration.

  • Available: DOCS-033

    OTLP and query reference

    Review route shapes, content types, tenant headers, query filters, error behavior, and local limits.

  • Available: DOCS-039

    OTLP and S3 query compatibility

    Separate live ingest and query behavior from S3 query-read scope, future publication work, and unsupported signal families.

  • Available: DOCS-063

    Example validation

    Validate example manifests, status labels, rendered routes, evidence links, validation modes, reviewers, and limits.

Guide Guardrails

Local Policy First

LogDB examples must show x-logdb-tenant and bearer-token requirements before readers adapt collector exporters or curl commands.

Collector Smoke Is Opt-In

The checked-in smoke runner is tested, but a live otelcol process run requires an approved collector binary and reviewer-accepted output.

S3 Boundaries Stay Separate

S3 query-read configuration is not S3 publication, and BYOC or external sink language needs separate evidence.