Menu

Operations

LogDB Operations

LogDB operations pages collect local ingest, query, WAL, segment bundle, S3 query-read, BYOC preflight, and support-review workflows without broadening product-bound storage or readiness claims.

Current availability

Private Beta. Public beta is scheduled for .

LiveConfirm First

Operations Scope

Start with the operator runbooks when local LogDB health, OTLP admission, WAL state, segment bundles, query troubleshooting, S3 query-read configuration, BYOC preflight, or support details need a reviewed path.

Operations Pages

  • Available

    LogDB operator runbooks

    OTLP admission failures, WAL and data-directory issues, segment bundle checks, query troubleshooting, S3 query-read boundaries, BYOC preflight, and support details.

  • Available

    Cross-product observability and audit guide

    Use shared health, metrics, audit, logs, diagnostics, support bundle support details, and privacy-safe handoff practices before escalation.

  • Available

    Troubleshooting index

    Start with symptom-oriented LogDB and cross-product entries before opening the exact product runbook.

  • Available

    Support bundle and privacy page

    Use support bundle contents, exclusions, redaction expectations, and approval checks before sharing LogDB limits and compatibility guidance.

  • Available

    LogDB OTLP and query reference

    Check route shapes, tenant headers, error mapping, query filters, limits, and S3 query-read boundaries.

  • Available

    LogDB configuration and BYOC reference

    Use startup settings, WAL modes, optional gRPC, S3 query-read settings, Terraform output, Helm values, and handoff preflight boundaries.

  • Available

    LogDB known limits

    Keep S3 publication, BYOC deployment readiness, public replay APIs, external sinks, metrics/profile support, and stronger readiness wording product-bound.

Operations Boundaries

Query Read Is Not Publication

LOGDB_QUERY_STORE=s3 changes the query read path only; it does not prove ingest publication to S3 or customer-owned bucket writes.

Capture Shape, Not Payload

Use status, error kind, query shape, bundle counts, and indexes while keeping raw telemetry payloads out of routine evidence packages.

Keep BYOC Preflight Bounded

Terraform, Helm, and preflight artifacts validate handoff shape, not full deployment readiness or support posture.