Retention model
Retention is project scoped.
Logister keeps active product data in PostgreSQL. Retention policies decide when older project telemetry can be deleted. Archive exports are optional and use Active Storage to write compressed JSONL before deletion.
Not a database backup
Telemetry archives do not replace PostgreSQL backups. They export selected event/span rows, not accounts, settings, API keys, memberships, or full workflow state.
Choose a page
Use the subpage that matches the work.
Policy
Choose retention windows
Understand hot events, trace spans, closed error groups, and archive-before-delete.
Storage
Configure archive storage
Set Active Storage, S3-compatible credentials, archive prefix, and object layout.
Jobs
Run and verify retention
Check scheduled sweeps, manual commands, recent archive runs, and failures.
Defaults
The default policy is conservative.
| Setting | Default |
|---|---|
| Hot events | 30 days |
| Trace spans | 30 days |
| Closed error groups | Keep indefinitely |
| Archive exports | Off |
| Archive before delete | Off |