Local Policy First
LogDB examples must show x-logdb-tenant and bearer-token requirements before readers adapt collector exporters or curl commands.
Guides
LogDB guides collect collector examples and decision support for local OTLP logs/traces ingest, retained-record query, tenant policy, and product-bound S3 or BYOC claims.
Current availability
Private Beta. Public beta is scheduled for .
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 product confirmation.
Available
LogDB OpenTelemetry Collector examplesTested collector config, smoke-runner commands, and curl examples for logs/traces ingest, retained-record query, tenant headers, and local policy boundaries.
Available
LogDB OTLP ingest and query quickstartUse the local curl workflow when readers need a copy/paste first-success path before adapting collector configuration.
Available
OTLP and query referenceReview route shapes, content types, tenant headers, query filters, error behavior, and local limits.
Available
OTLP and S3 query compatibilitySeparate live ingest and query behavior from S3 query-read scope, future publication work, and unsupported signal families.
Available
Example validationValidate example manifests, status labels, rendered routes, limits links, validation modes, support teams, and limits.
LogDB examples must show x-logdb-tenant and bearer-token requirements before readers adapt collector exporters or curl commands.
The checked-in smoke runner is tested, but a live otelcol process run requires an approved collector binary and accepted output.
S3 query-read configuration is not S3 publication, and BYOC or external sink language needs separate evidence.