Capture Before Remediation
Runbooks should collect status codes, counters, logs, timestamps, route names, and sanitized symptoms before a state-changing step can alter the signal.
Operations
Confirm FirstRunbooks, diagnostics, troubleshooting, and support paths.
Use operations pages to move from symptoms to safe checks, diagnosis, remediation, escalation, and privacy-aware support handoff without turning bounded operational behavior into a stronger public claim.
Operations Index
- ObjectDB operator runbooks
Available
Health checks, platform capabilities, S3 gateway limits, local adapter caveats, and support-safe diagnostics.
- Message Broker operator runbooks
Available
Health, metrics, audit, diagnostics, storage inspection, quota rejection, replication status boundaries, and support-safe diagnostics.
- LogDB operator runbooks
Available
OTLP admission, WAL, segment bundle, query troubleshooting, S3 query-read boundaries, BYOC preflight, and support-safe diagnostics.
- Observability and audit guide
Available
Cross-product health, metrics, audit, logs, diagnostics, support bundle guidance, and privacy-safe handoff practices.
- Troubleshooting index
Available
Symptom-oriented troubleshooting entries organized by product, first check, likely cause, next action, diagnostic context, and runbook route.
- Support bundle and privacy page
Available
Support bundle contents, exclusions, redaction expectations, escalation triggers, and privacy boundaries.
Operations Boundaries
Privacy-Aware Handoff
Support bundles, logs, traces, tokens, tenant data, and customer payloads need explicit redaction guidance before sharing.
Stay Within Product Limits
If an observed behavior touches availability, durability, performance, scale, or security, keep the public wording scoped to the product status, limits, and compatibility pages.