LogisterDocumentationRetention policy
Data retention / Policy

Choose how long each kind of project data remains easy to review.

Use Project > Settings > Data when older project activity should leave normal product views, or when closed errors should be kept longer than raw activity.

Before you start

Test retention changes on a low-risk project first.

Retention settings remove old data from normal product views after background jobs run. Before shortening a window on an important project, decide whether the team needs archive files, confirm the worker is running, and use the jobs page to run a dry verification pass.

DecisionUse this setting
Old non-error telemetry can leave Events and Insights after a fixed window.Hot event retention.
Old span waterfalls can leave performance detail after a fixed window.Trace span retention.
Closed error groups should stay longer than raw telemetry.Closed error retention.
Old rows should be written to archive files.Archive retained data.
Cleanup should stop unless the archive write succeeds first.Require archive before deletion.

Fields

Each field controls a separate cleanup scope.

Logister Data settings page showing the collapsed retention policy summary and Archive Center overview.
Saved settings collapse into a short summary row. Expand the row to edit retention windows or archive behavior.
FieldWhat it means in the UI
Hot event retentionHow long logs, metrics, transactions, and check-ins stay available in day-to-day activity views.
Trace span retentionHow long request timing and waterfall-style span detail stays available for performance review.
Closed error retentionHow long resolved, ignored, or archived error groups stay available after the team has handled them. Blank means keep closed groups indefinitely.
Archive retained dataAllow Logister to write gzip JSONL archive files to the configured archive service.
Require archive before deletionDo not remove matching data unless its archive export succeeds first. This option depends on Archive retained data.

Verify

Make sure cleanup behaves before relying on it.

  1. Save the policy on a low-risk project.
  2. Run a dry retention job or wait for the scheduled worker pass.
  3. Open Project > Settings > Data and check Archive Center if archive retained data is enabled.
  4. Use Coverage to confirm each scope has the status you expected, then use Catalog to inspect recent archive runs and object keys.
  5. Open Events, Insights, Performance, or closed error views and confirm old data changed only in the scope you expected.

Use jobs and verification for manual commands and archive-run checks.

Troubleshooting

Separate policy choices from worker execution.

SymptomWhat to check
Nothing changed after savingRetention runs in the background. Confirm Sidekiq is running or run a controlled verification command.
Require archive before deletion blocks cleanupArchive storage may be missing or failing. Fix archive storage before expecting rows to be removed.
Closed errors disappeared sooner than expectedCheck closed error retention separately from hot event and trace span retention.
Events changed but spans did notHot event retention and trace span retention are separate scopes.