Start With Local Evidence
Use health, platform capabilities, and S3 Core smoke output before changing local state or escalating a support case.
Operations
ObjectDB operations pages collect local health checks, platform capability checks, S3 Core smoke workflows, data-directory safety, common error triage, unsupported S3 boundaries, and support evidence handoff.
Current availability
Private Beta. Public beta is scheduled for .
Start with the operator runbooks when local ObjectDB startup, health, S3 Core smoke, data-directory checks, unsupported S3 requests, or support evidence capture needs a reviewed path.
Available: DOCS-050
ObjectDB operator runbooksHealth checks, platform capabilities, S3 Core smoke, data-directory checks, unsupported S3 behavior, common errors, and support evidence.
Available: DOCS-054
Cross-product observability and audit guideUse shared health, metrics, audit, logs, diagnostics, support bundle evidence, and privacy-safe handoff practices before escalation.
Available: DOCS-055
Troubleshooting indexStart with symptom-oriented ObjectDB and cross-product entries before opening the exact product runbook.
Available: DOCS-056
Support bundle and privacy pageUse support bundle contents, exclusions, redaction expectations, and approval gates before sharing ObjectDB evidence.
Available: DOCS-022
ObjectDB S3 Core quickstartRun the local bucket/object workflow that the operator smoke test reuses for first checks.
Available: DOCS-030
ObjectDB configuration referenceCheck bind address, data directory, base domains, fixed S3 ingress limits, and platform capability requirements.
Available: DOCS-042
ObjectDB known limitsSeparate unsupported S3 families, local adapter constraints, and review-bound claims before escalating incidents.
Use health, platform capabilities, and S3 Core smoke output before changing local state or escalating a support case.
Run cleanup only against the disposable smoke directory named by the runbook; never remove a shared ObjectDB data path by habit.
Versioning, Object Lock, lifecycle, replication, inventory, notifications, SelectObjectContent, ACLs, and website hosting are known limits, not operator incidents by themselves.