LogDB known limits.

Known LogDB unsupported behavior, signal-scope exclusions, S3 query-read limits, BYOC boundaries, and review-required claim areas.

Current availability

Private Beta. Public beta is scheduled for November 2, 2026.

Audience

Use this page before choosing LogDB signal routes, describing S3 or BYOC behavior, or reviewing claims that mention replay, external sinks, support, security, performance, or scale.

Maturity Status

Live Ingest And Query

Live

Logs, traces, endpoint helpers, optional gRPC, and local retained-record query stay tied to the OTLP and query reference.

Review-Bound Storage Direction

Verification Required

S3 query-read, BYOC handoff, tenant policy wording, replay foundations, and support wording need reviewer acceptance before promotion.

Scope

LogDB OTLP logs/traces ingest, endpoint helpers, optional gRPC, local query, S3 query-read selection, replay foundations, BYOC handoff, and unsupported signal families.

Prerequisites

Read the LogDB OTLP and S3 query compatibility matrix.
Use the OTLP/query and configuration references for exact route and setting behavior.

Current Limits

LogDB known limits. current limits
Limit	Applies to	Runtime behavior	Next best path	Evidence
Metrics and profiles ingest	OTLP signal scope	Current LogDB docs cover logs, traces, retained segment search, and replay foundations only. Metrics and profiles are outside the documented route surface.	Use OTLP logs and traces routes that are documented in the reference.	LDB-EVID-006, LDB-EVID-008, LDB-EVID-010
Live ingest publication to S3	S3-backed publication claims	LOGDB_QUERY_STORE=s3 changes only the query read path for retained segment bundles. Ingest still writes through the local data and WAL path.	Describe S3 as query-read configuration only until publication evidence is accepted.	LDB-EVID-005, LDB-EVID-009, LDB-EVID-010
Public replay APIs and external sinks	Replay coordinator foundations	Local coordinator, checkpoint, and audit evidence can be discussed as preview foundations; public replay APIs and external sinks remain future-facing.	Keep examples on documented ingest and query APIs.	LDB-EVID-006, LDB-EVID-010
BYOC deployment readiness	AWS BYOC package and customer-owned storage direction	Terraform, Helm, and offline preflight artifacts exist, but deployment readiness and customer-owned S3 publication require operations and security acceptance.	Use the configuration and BYOC reference for current handoff boundaries.	LDB-EVID-009, LDB-EVID-010

Unsupported Behavior

LogDB known limits. unsupported behavior
Scenario	What happens	Recommended action
Send metrics or profiles as if they are documented signals	Those signal families are outside the current LogDB route surface.	Use documented logs and traces routes and track metrics/profile needs as future compatibility work.
Configure S3 query-read expecting ingest publication to S3	The S3 setting affects query reads only; ingest continues through the local data and WAL path.	Document S3 query-read separately from S3 publication.
Build against public replay APIs or external replay sinks	Only replay foundations are documented today; public APIs and external sinks remain future-facing.	Keep integrations on ingest and query APIs until replay docs and evidence land.

Claims Requiring Review

LogDB known limits. review-bound claims
Claim area	Required reviewer	Publication status
S3 publication or customer-owned bucket writes	logdb-product-sme, operations-reviewer, and security-reviewer	Verification Required
BYOC deployment readiness	operations-reviewer and security-reviewer	Verification Required
Observability replacement, support, security, performance, or scale wording	logdb-product-sme, support-reviewer, and docs lead	Verification Required

Evidence

LogDB known limits. evidence
Limit or unsupported behavior	Evidence	Status
Signal exclusions and query boundaries	DOCS-033, DOCS-039, LDB-EVID-008, and LDB-EVID-010	pending
Configuration, S3 query-read, and BYOC boundaries	DOCS-034, LDB-EVID-009, and LDB-EVID-010	pending
LogDB limits page artifact	DOCS-042	pending

The evidence table summarizes the reviewed basis for each known limit without exposing internal source locations.

Limits

This page summarizes current LogDB ingest, query, S3 query-read, replay, and BYOC boundaries.
Do not use S3 query-read configuration as evidence for live S3 publication.
Metrics, profiles, public replay APIs, external sinks, and stronger readiness wording need new evidence before promotion.

Safe Next Steps

Available: DOCS-039
Compare OTLP and query scope
Use row status and evidence before relying on ingest, query, S3, signal, or BYOC behavior.
Available: DOCS-033
Read OTLP and query reference
Check route shapes, headers, limits, errors, and query filters.
Available
Review LogDB evidence
Confirm source records before strengthening LogDB limits wording.