Retention isn't applied
Weik.io 2026.2A telemetry store runs with a different number of days than you set in the installation's settings.
| Kind | Severity | Who sees it |
|---|---|---|
retention- |
Warning, and an error while a store keeps fewer days than set | Platform administrators, in a list that isn’t narrowed to an environment or a project |
What it means#
A store that keeps more days than you set uses more disk. A store that keeps fewer days deletes records you expect to have.
You set the days each store keeps in the installation’s settings.
| Store | Days in a new installation |
|---|---|
| Log store | 30 |
| Metric store | 90 |
| Trace store | 7 |
What raises it#
When the store didn’t start with the days you set and still runs with its earlier days, the problem shows at the next check, within 30 seconds. When the store runs with other days for another reason, the problem shows after two minutes. That happens when you set fewer days without confirming that older records are erased, or when the backend hasn’t changed the store. It’s an error while the store keeps fewer days than you set.
What to check#
On a hub server, in the stack’s folder, run weikio-backend doctor:
$ docker compose run --rm infra weikio-backend doctorThe retention lines of doctor show the days you set and the days each store runs with.
Read the store’s log. For the log store, run:
$ docker compose logs --tail 50 victoria-logsHow to fix it#
When the store didn’t start with the days you set, restart it. While the store restarts, the hub keeps the incoming telemetry and sends it on once the store answers. To restart the log store, run:
$ docker compose restart victoria-logsThe metric store is victoria-metrics and the trace store victoria-traces.
When you set fewer days without confirming that older records are erased, set the days again. For the log store, run:
$ weikio settings set --logs-retention <days>dThe command lists what the shorter retention erases. To confirm, answer yes or add --yes.
When the backend hasn’t changed the store, read the backend’s log in the stack’s folder:
$ docker compose logs backend