Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Documentation Grafana Mimir Operator and user guide Configuration Configure metrics storage retention

Configure Grafana Mimir metrics storage retention

Grafana Mimir stores the metrics in a object storage.

By default, metrics that are stored in the object storage are never deleted, and the storage utilization will increase over time. You can configure the object storage retention to automatically delete all of the metrics data older than the configured period.

Configure the storage retention

The compactor is the Mimir component that is responsible for enforcing the storage retention. To configure the storage retention, set the CLI flag -compactor.blocks-retention-period or change the following YAML configuration:

yaml Copy

limits:
  # Delete from storage metrics data older than 1 year.
  compactor_blocks_retention_period: 1y

To configure the storage retention on a per-tenant basis, set overrides in the runtime configuration:

yaml Copy

overrides:
  tenant1:
    # Delete from storage tenant1's metrics data older than 1 year.
    compactor_blocks_retention_period: 1y
  tenant2:
    # Delete from storage tenant2's metrics data older than 2 years.
    compactor_blocks_retention_period: 2y
  tenant3:
    # Disable retention for tenant3's metrics (never delete its data).
    compactor_blocks_retention_period: 0

Per-series retention

Grafana Mimir doesn’t support per-series deletion and retention, nor does it support Prometheus’ Delete series API.