Start With Local status notes
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 details 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 details capture needs a reviewed path.
Available
ObjectDB operator runbooksHealth checks, platform capabilities, S3 Core smoke, data-directory checks, unsupported S3 behavior, common errors, and support details.
Available
Cross-product observability and audit guideUse shared health, metrics, audit, logs, diagnostics, support bundle details, and privacy-safe handoff practices before escalation.
Available
Troubleshooting indexStart with symptom-oriented ObjectDB and cross-product entries before opening the exact product runbook.
Available
Support bundle and privacy pageUse support bundle contents, exclusions, redaction expectations, and approval checks before sharing ObjectDB limits and compatibility guidance.
Available
ObjectDB S3 Core quickstartRun the local bucket/object workflow that the operator smoke test reuses for first checks.
Available
ObjectDB configuration referenceCheck bind address, data directory, base domains, fixed S3 ingress limits, and platform capability requirements.
Available
ObjectDB known limitsSeparate unsupported S3 families, local adapter constraints, and product-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.