Live Ingest And Query
LiveOTLP HTTP/protobuf, OTLP JSON compatibility, custom endpoint helpers, optional gRPC, and local retained-record query are grounded in the LogDB OTLP and query reference.
Compatibility
LogDB OTLP and S3 query compatibility matrix.
Compatibility matrix for LogDB OTLP ingest, optional gRPC, local query, S3 query-read selection, explicit signal exclusions, and future S3 publication work.
Current availability
Private Beta. Public beta is scheduled for .
LivePreviewConfirm First
Matrix Snapshot
- Matrix rows
- 12
- Status values
- 6
- Query stores
- 2
Audience
Use this matrix when deciding whether a LogDB ingest, query, S3, or signal-scope behavior is active, locally bounded, unsupported, preview-only, future-facing, or still waiting on product confirmation.
Readiness Notes
S3 And BYOC Boundary
Confirm FirstS3 query-read selection, customer-owned storage direction, tenant policy language, and BYOC handoff remain product-bound. S3 publication is future work.
Compatibility Scope
Ingest Surface
The matrix covers custom endpoint helpers, native OTLP HTTP/protobuf, OTLP JSON compatibility, and optional OTLP/gRPC logs and traces.
Query Surface
Local segment query is active by default. S3 query-read can be configured, but that does not make ingest publish to S3.
Signal Boundary
Metrics and profiles are explicit exclusions. Current LogDB docs stay focused on logs, traces, retained segment search, and replay foundations.
Status Legend
Supported
Implemented and validated for the exact documented scope.
Partial
Some behavior works, but documented gaps, limits, or exclusions apply.
Unsupported
Not implemented, intentionally unavailable, or rejected at runtime.
Preview
Early surface for planning or evaluation before complete customer-facing support.
Future
Planned direction with no current runtime behavior to rely on. Check the documented status and release notes before using it.
OTLP And Query Matrix
| Capability | Status | Maturity | Notes |
|---|---|---|---|
| Native OTLP HTTP/protobuf logs and traces | Supported | Live | POST /v1/logs and POST /v1/traces accept OTLP protobuf batches with tenant headers and WAL-backed publication. |
| OTLP HTTP JSON compatibility logs and traces | Supported | Live | POST /v1/otlp/logs and POST /v1/otlp/traces accept OpenTelemetry-shaped JSON, enforce tenant admission, and return deterministic record IDs. |
| Custom endpoint JSON helpers | Supported | Live | POST and GET /v1/endpoint/{activation_id} helper routes are implemented but remain separate from the tenant-admitted OTLP contract. |
| Optional OTLP/gRPC logs and traces | Partial | Live | Generated LogsService and TraceService export methods run only when LOGDB_OTLP_GRPC_BIND_ADDRESS is configured. |
| Local retained-record query | Supported | Live | POST /v1/query reads local segment bundles by dataset, exact record ID, exact trace ID, time filters, pagination, and deadline controls. |
| Configured S3 query-read store | Partial | Confirm First | LOGDB_QUERY_STORE=s3 changes only the POST /v1/query read path for retained segment bundles. Ingest still writes through the local data and WAL path. |
| Tenant admission and query authorization | Confirm First | Confirm First | Local policy requires x-logdb-tenant, bearer credentials, matching OTLP tenant claims, dataset authorization, and quota checks; security review must accept external wording. |
| Ingest and query limits | Partial | Confirm First | OTLP batches cap at 512 records, gateway budgets are configurable, tenant windows apply, query pages default to 100 and cap at 500. |
| Metrics and profiles ingest | Unsupported | Confirm First | Current LogDB docs cover logs, traces, retained segment search, and replay foundations only. Metrics and profiles are outside the documented route surface. |
| Live ingest publication to S3 | Future | Future | S3-backed publication needs approved-bucket conformance, operations evidence, and release review before it can be documented as active behavior. |
| Replay coordinator foundations | Preview | Preview | Local coordinator, checkpoint, and audit support details can be discussed as preview foundations; public replay APIs and external sinks remain future-facing. |
| AWS BYOC package and customer-owned storage direction | Confirm First | Confirm First | Terraform, Helm, and offline preflight artifacts exist, but full deployment readiness and customer-owned S3 publication require operations and security acceptance. |
Current Limits
| Limit | Value | Applies to |
|---|---|---|
| OTLP batch size | 512 records | HTTP/protobuf logs, HTTP/protobuf traces, JSON compatibility logs and traces, and gRPC exports |
| OTLP gateway in-flight requests | 64 by default | Shared HTTP and gRPC ingest backpressure |
| OTLP gateway in-flight records | 8192 by default | Shared HTTP and gRPC ingest backpressure |
| OTLP gateway in-flight bytes | 33554432 by default | Shared HTTP and gRPC ingest backpressure |
| Tenant admission window | 10000 records, 16 MiB, 16 concurrent requests per 60 seconds | Local development tenant policy and policy-derived ingest checks |
| Query page size | Default 100, maximum 500 | POST /v1/query |
| Endpoint recent readback | 100 records | GET /v1/endpoint/{activation_id}/recent_100 |
| Query store selection | Local by default, S3 query-read when configured | Query read path only |
Explicit Exclusions
Metrics ingest, profiles ingest, dashboarding, SIEM replacement, public replay APIs, external sinks, and live S3 publication are outside the active LogDB route surface described by this matrix.
Source scope
| Matrix area | Source scope | Status | Last reviewed |
|---|---|---|---|
| OTLP and query route surface | documented source scope, and documented source scope | Source-scoped | 2026-08-16 |
| Quickstart-supported workflow | documented source scope and /products/logdb/quickstart/ | Source-scoped | 2026-08-16 |
| S3 query-read and BYOC configuration | documented source scope | Source-scoped | 2026-08-16 |
| Compatibility page artifact | documented source scope and docs/compatibility/documented source scope-logdb-otlp-s3-query-compatibility.md | Source-scoped | 2026-08-16 |
Internal public documentation boundaries track this LogDB compatibility matrix and the review note required to change row status.
Limits
This matrix covers current LogDB ingest and query documentation only. It does not approve S3 publication, BYOC deployment readiness, public replay APIs, external sinks, support, availability, performance, scale, security, compliance, or GA claims.
See the OTLP and query reference for route behavior and the configuration and BYOC reference for S3 query-read settings.
Safe Next Steps
Available
Run OTLP ingest and query quickstartExercise OTLP JSON compatibility ingest, exact-record query, trace pagination, tenant headers, and cleanup.
Available
Read OTLP and query referenceUse route shapes, tenant headers, query filters, limits, errors, and S3 query-read boundary language behind each matrix row.
Available
Read configuration and BYOC referenceCheck local runtime settings, optional gRPC bind, WAL modes, S3 query-read variables, and BYOC handoff limits.
Available
Review LogDB limitsCheck source records before expanding LogDB S3, BYOC, replay, support, security, or operational wording.
Available
Read known limitsSee metrics/profile exclusions, S3 query-read behavior, replay API, external sink, and BYOC boundaries.
Available
Compare compatibility modelUse the workflow for stale-row checks, status-note refresh, owner review, and release-note updates.
