LogisterDocumentationRetention jobs
Data retention / Jobs

Verify retention before pruning real data.

Retention runs through background jobs. Use dry runs and recent archive rows before trusting archive-before-delete on important projects.

Commands

Use manual commands for verification and maintenance windows.

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 UI and the bucket.

  1. Run a dry retention pass and confirm candidate counts.
  2. Run retention on a low-risk project.
  3. Open Project > Settings > Data and review Recent archive runs.
  4. Confirm the .jsonl.gz objects exist in object storage.
  5. Download one object, decompress it, and confirm each line parses as JSON.

Failures

Retention failures should be visible.

Failed archive runs are recorded with an error message and can send retention failure notifications. If archive-before-delete is enabled, fix storage first, then rerun retention.