DOCS-113 and DOCS-114
Still owns
Cross-product concepts, operations, support, privacy, community, roadmap source notes, and generated metadata.
DOCS-112
Verification RequiredLogDB verification dispositions.
This launch-readiness review decides how LogDB hub, quickstart, compatibility rows, OTLP/query references, configuration and BYOC references, limits, evidence, guides, collector examples, and operator runbooks keep or bound Verification Required labels before final launch acceptance.
Decision Snapshot
- LogDB routes
- 12
- Source groups
- 1
- Rows reviewed
- 12
- P0/P1 blockers
- 0
- Product lanes open
- 0
Route Dispositions
| Route or surface | Current exposure | Disposition | Rationale | Evidence |
|---|---|---|---|---|
| LogDB hub | Controlled Beta product hub with live ingest, WAL, segment bundle, query, preview replay, future S3 publication, and gated BYOC wording. | Accept with limits | The hub separates current local route behavior from S3 publication, BYOC, replay API, scale, support, security, and GA claims. | LDB-EVID-001, LDB-EVID-005, and LDB-EVID-006 |
| OTLP ingest and query quickstart | Local OTLP JSON compatibility ingest, deterministic record IDs, retained-record query, pagination, tenant headers, rejection checks, and cleanup. | Accept with limits | The workflow proves local logs/traces ingest and query behavior while keeping collector, S3, replay, BYOC, support, scale, and GA wording out of the success path. | LDB-EVID-002 through LDB-EVID-007 and DOCS-024 |
| Compatibility matrix | Row labels separate supported, partial, unsupported, preview, future, and verification-required OTLP, query, S3, BYOC, and signal boundaries. | Accept with limits | The matrix keeps S3 query-read, tenant policy, limits, unsupported signals, S3 publication, replay, and BYOC claim boundaries visible until owners accept narrower promotion. | LDB-EVID-008, LDB-EVID-010, and DOCS-039 |
| Reference index | Reference-family entry under live and Verification Required maturity labels. | Accept with limits | The index routes readers to exact runtime and configuration behavior without broadening LogDB product-family claims. | DOCS-033, DOCS-034, and DOCS-039 |
| OTLP and query reference | Source-backed routes for endpoint JSON helpers, native OTLP HTTP/protobuf, OTLP JSON compatibility, optional gRPC, tenant admission, query, limits, and errors. | Accept with limits | Current route shapes and limits are useful, but tenant admission, query-store selection, external security, support, and production readiness wording remains review-bound. | LDB-EVID-001 through LDB-EVID-004, LDB-EVID-008, and DOCS-033 |
| Configuration and BYOC reference | Runtime env vars, S3 query-read settings, WAL durability modes, optional gRPC bind, Terraform values, Helm values, and offline preflight boundaries. | Accept with limits | Local runtime settings can be documented, while replicated-local WAL, S3 query-read, Terraform-to-Helm handoff, retained customer data, and deployment-readiness wording need operations and security acceptance. | LDB-EVID-005, LDB-EVID-009, and DOCS-034 |
| Known limits | Metrics/profile exclusions, S3 query-read versus publication behavior, replay boundaries, external sink boundaries, BYOC limits, and sensitive claim gates. | Accept with limits | The page directly owns the unresolved claim areas, so the conservative label reduces launch risk instead of hiding it. | LDB-EVID-006, LDB-EVID-010, LDB-EVID-011, and DOCS-042 |
| Evidence index | Evidence records remain owner-pending and page maturity remains Verification Required. | Accept with limits | The evidence tracker prevents pending product, security, operations, support, privacy, and docs QA records from becoming approved customer commitments. | LDB-EVID-001 through LDB-EVID-013 |
| Guides and collector examples | Guide family points to local OpenTelemetry Collector examples and keeps review-bound wording. | Accept with limits | The guide pages keep example discovery available without making broader observability, S3, replay, BYOC, support, or scale promises. | LDB-EVID-013 and DOCS-060 |
| Operations and operator runbooks | Runbooks cover health, OTLP admission failures, WAL/data-directory triage, segment checks, query troubleshooting, S3 query-read, BYOC preflight, and support evidence. | Accept with limits | The runbooks make redaction, non-destructive handling, S3 read/publication distinction, and BYOC preflight boundaries explicit without approving production incident response. | LDB-EVID-003, LDB-EVID-004, LDB-EVID-005, LDB-EVID-009, LDB-EVID-012, and DOCS-052 |
Compatibility Row Dispositions
| Row area | Current state | Disposition | Rationale |
|---|---|---|---|
| Native OTLP HTTP/protobuf logs and traces | Supported / Live | Keep live with scope | Routes accept documented logs/traces protobuf batches with tenant headers and local WAL-backed publication evidence; this does not imply metrics, profiles, or production support. |
| OTLP HTTP JSON compatibility logs and traces | Supported / Live | Keep live | JSON compatibility is local-route and test-backed, including tenant admission and deterministic record IDs. |
| Custom endpoint JSON helpers | Supported / Live | Keep live but separate | Endpoint helpers are useful local JSON routes, but they are explicitly separate from the tenant-admitted OTLP contract. |
| Optional OTLP/gRPC logs and traces | Partial / Live | Keep live when configured | Generated services run only when LOGDB_OTLP_GRPC_BIND_ADDRESS is configured, so partial status keeps setup requirements visible. |
| Local retained-record query | Supported / Live | Keep live with local query limits | POST /v1/query supports dataset, exact ID, trace ID, time, pagination, and deadline filters over retained segment bundles. |
| Configured S3 query-read store | Partial / Verification Required | Accept with limits | S3 selection changes the query read path only; it is not evidence for ingest publication or customer-owned bucket writes. |
| Tenant admission and query authorization | Verification Required / Verification Required | Accept with security boundary | Local headers, bearer token, matching OTLP tenant claims, dataset authorization, and quota language need security acceptance before stronger external wording. |
| Ingest and query limits | Partial / Verification Required | Accept with limit-bound wording | Batch caps, gateway budgets, tenant windows, and query page limits are documented, but product and operations reviewers still own promotion. |
| Metrics and profiles ingest | Unsupported / Verification Required | Keep unsupported and review-bound | Current docs deliberately cover logs, traces, retained segment query, and replay foundations only. |
| Live ingest publication to S3 | Future / Future | Keep future | Approved-bucket conformance, operations evidence, and release review are required before S3-backed publication can be described as active behavior. |
| Replay coordinator foundations | Preview / Preview Contract | Keep preview contract | Local coordinator, checkpoint, and audit evidence is useful, but public replay APIs and external sinks remain future-facing. |
| AWS BYOC package and customer-owned storage direction | Verification Required / Verification Required | Accept with operations/security limits | Terraform, Helm, and offline preflight artifacts exist, but full deployment readiness and customer-owned S3 publication need operations and security acceptance. |
Launch Blocking Rules
| Severity | Condition | Required action |
|---|---|---|
| P0 | A LogDB route exposes private source paths, credentials, raw telemetry, customer data, destructive BYOC cleanup instructions, or unsupported security/legal/support promises. | Remove the exposure before launch review continues. |
| P1 | A core LogDB page presents S3 query-read as ingest publication, BYOC handoff as deploy-ready, metrics/profiles as supported, public replay APIs or external sinks as active, or production support/security/GA/performance/scale as approved. | Rewrite, relabel, or block through DOCS-104. |
| P2 | A page or row keeps Verification Required because tenant/security, S3 query-read, WAL durability, BYOC, limits, collector smoke, owner review, or sensitive claim evidence is pending while nearby copy names the boundary. | Accept with limits and keep the evidence or known-limit path visible. |
| P3 | Source notes, README, generated manifests, project-management records, or automation mention LogDB labels as review taxonomy. | Keep as tracker language unless DOCS-114 changes it. |
Remaining Boundaries
DOCS-104
Still owns
Exact build, reviewer signoffs, accepted risks, launch watch, and go/no-go decision.