Recover From a Problem
Recover From a Problem
Most Custd repair paths are self-healing. Your first job is to identify which subsystem is unhealthy, then confirm recovery.
| Symptom | Likely subsystem |
|---|---|
| Events accepted but not appearing | Ingest, NATS, or segment writer |
| Rollups or compaction lagging | Scheduler, rollups, or compactor |
| Generated test data needs cleanup | Data lifecycle tooling |
| Data loss or corruption | Backup and restore |
Start with See What Is Happening. If the status page points to an operator-only repair, capture the failing subsystem, time range, and tenant before handing the issue to your Custd operator.