Dears
I am trying to configure Mimir version 2.12.0 (using it from a binary) to use different retention policies for different tenants as described in Configure Grafana Mimir metrics storage retention | Grafana Mimir documentation
Following the documentation, I added the following to my configuration file:
multitenancy_enabled: true
blocks_storage:
backend: filesystem
bucket_store:
sync_dir: /var/lib/mimir/tsdb-sync
filesystem:
dir: /var/lib/mimir/data/tsdb
tsdb:
dir: /var/lib/mimir/tsdbcompactor:
data_dir: /var/lib/mimir/compactor
sharding_ring:
kvstore:
store: memberlistoverrides:
FirstServer:
# Delete from storage tenant1’s metrics data older than 1 year.
compactor_blocks_retention_period: 1y
SecondServer:
# Delete from storage tenant2’s metrics data older than 2 years.
compactor_blocks_retention_period: 2y
ThirdServer:
# Disable retention for tenant3’s metrics (never delete its data).
compactor_blocks_retention_period: 0[…]
However, when trying to start Mimir, I get the following error:
Aug 14 19:26:33 alloy-mimir-server systemd[1]: Started Horizontally scalable, highly available, multi-tenant, long term Prometheus…
Aug 14 19:26:33 alloy-mimir-server mimir[12084]: error loading config from /etc/mimir/config.yml: Error parsing config file: yaml: unmarshal errors:
Aug 14 19:26:33 alloy-mimir-server mimir[12084]: line 21: field overrides not found in type mimir.Config
Aug 14 19:26:33 alloy-mimir-server systemd[1]: mimir.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 19:26:33 alloy-mimir-server systemd[1]: mimir.service: Failed with result ‘exit-code’.
Aug 14 19:26:34 alloy-mimir-server systemd[1]: mimir.service: Scheduled restart job, restart counter is at 1.
Is there any option I need to use at startup to load a module that allows me to use this feature?
Thanks