LogisterDocumentationRetention jobs
Data retention / Jobs

Verify cleanup before trusting it on important projects.

The Data tab includes Archive Center because users need proof that archive writes and cleanup are working. Use that visible history before requiring archives before deletion on an important project.

Maintenance

Use manual commands when you need a controlled verification pass.

shell
DRY_RUN=true bin/rails "logister:telemetry:retention"
bin/rails "logister:telemetry:archive[ingest_events,30]"
bin/rails "logister:telemetry:archive[trace_spans,30]"
CONFIRM=prune bin/rails "logister:telemetry:prune_hot[30]"

Verify

Check the Data tab first.

  1. Use a low-risk project before changing retention on important projects.
  2. Open Project > Settings > Data and review Archive Center.
  3. Use Overview for the overall state, Coverage for each retention scope, and Catalog for recent archive runs and object keys.
  4. Confirm the latest relevant run succeeded before enabling Require archive before deletion more broadly.
  5. If your team uses archive storage, confirm the matching .jsonl.gz object exists and can be opened.

Failures

Retention failures should be visible.

Failed archive runs should appear in Archive Center and can send retention failure notifications. If Require archive before deletion is enabled, treat a failure as a stop sign: fix the archive problem first, then run cleanup again.