Known limits

LogDB known limits.

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

Current availability

Private Beta. Public beta is scheduled for December 14, 2026.

LivePreviewConfirm First

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.

Readiness Notes

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

Confirm First

S3 query-read, BYOC handoff, tenant policy wording, replay foundations, and support wording need product confirmation 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
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.
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 behavior is publicly documented.
Public replay APIs and external sinks	Replay coordinator foundations	Local coordinator, checkpoint, and audit support details can be discussed as preview foundations; public replay APIs and external sinks remain future-facing.	Keep examples on documented ingest and query APIs.
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.

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 land.

Limits

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

Safe Next Steps

Available
Compare OTLP and query scope
Use row status and notes before relying on ingest, query, S3, signal, or BYOC behavior.
Available
Read OTLP and query reference
Check route shapes, headers, limits, errors, and query filters.
Available
Review LogDB limits
Confirm LogDB limits before planning broader replay, S3, or BYOC claims.