Acceldata
 Pulse
Search documentation… ⌘K

Last updated: Oct 29, 2026 11:49 UTC

Data Retention

Data Retention, previously known as Gauntlet, automatically removes old Pulse data based on configured retention settings. It helps control storage growth by periodically cleaning data from MongoDB, Elasticsearch, and VM/TSDB storage.

Starting with Pulse 4.2.0, you can manage Data Retention directly from the Pulse UI. The earlier CLI and YAML-based configuration workflows are no longer supported for customer configuration.

Navigation

  • In the Pulse UI, select Tools from the left navigation menu.
  • Select Data Retention.

Note

Before changing cluster-specific settings or viewing cleanup history, select the required cluster from the cluster switcher.

Supported Storage

Data Retention manages cleanup for the following storage types:

  • MongoDB: Removes old documents from configured Pulse collections and compacts storage when required.
  • Elasticsearch: Removes old indices, such as log and audit indices.
  • VM / TSDB: Manages metrics retention based on the configured retention period.

Explore in Detail

  • Data Retention Overview: View scheduler status, the next scheduled cleanup, current retention values, and the last cleanup. You can also start the scheduler or run cleanup manually.
  • Configure Data Retention: Configure global settings such as the cleanup schedule and VM retention, and cluster-specific settings for MongoDB and Elasticsearch retention.
  • View Data Retention History: View MongoDB and Elasticsearch cleanup history, including when cleanup ran, how it was initiated, what data was removed, and the approximate space freed.