Statistics and disk usage
Statistics
The Statistics page shows CPU, memory and disk for the host and for each managed container, as sparklines over a rolling window. Samples are collected continuously and kept in a ring buffer, so the page answers "what has this server been doing" rather than only "what is it doing now".
This is the honest check on tuning: worker counts sized for a peak that never happens cost memory every hour of every day.
Disk usage
The Disk usage page breaks down where space has gone: the instance data trees, backups, archives, Docker images, volumes and build cache.
Docker is usually the surprise. Per-instance images accumulate as instances are rebuilt, and the build cache grows quietly. Removing images an instance no longer uses is one of the built-in maintenance operations.
prod-1# odoocli instance image list --instance acmeprod-1# odoocli instance image remove --instance acmeSizes
prod-1# odoocli instance size --instance acmeprod-1# odoocli instance database size --instance acmeBackups are the other half
The disk usage page counts your backup directory only if it is on this server. Local backups on separate storage, and everything at an FTP, S3 or Azure target, are outside its view.
Retention is per target for exactly this reason: a local target keeping a week and an off-site target keeping a year is a normal arrangement, and the local disk should be sized for the week.