Metrics history & resolution
Metrics are kept at two levels of detail, and there is nothing to configure or pay attention to — charts pick the right one from the time range you select:
| Detail | Kept for |
|---|---|
| Per-minute (as collected) | 35 days |
| Hourly summary | 400 days |
The hourly summary is built continuously from the per-minute data: gauge-style metrics (CPU, memory, temperatures) keep their hourly average, counter-style metrics (network and disk totals) their hourly progression.
How charts choose
Section titled “How charts choose”The chart range picker runs from 1H to 1Y. Ranges up to 24 hours draw per-minute points, ranges up to 30 days hourly averages, and longer ones two-hour averages. A custom range that starts more than 32 days ago draws two-hour averages from the hourly summaries, however short it is, so any day in the last 32 days can be opened minute by minute, a few days inside the 35 that per-minute data is kept. Either way a chart’s right edge is current — a 3-month chart still ends at now, not at the last completed hour.
Two things follow from the resolution switch:
- A short spike — a two-minute CPU burst, say — is visible on ranges up to 24 hours within the last 32 days, but flattens into its hourly average on longer ranges. If a brief event from months ago matters, the alert incident it fired is a better record than the chart.
- The per-chart stats (Cur/Avg/p95/Max) are computed from the points the chart is showing, so they follow the same resolution as the chart itself.
When data is deleted
Section titled “When data is deleted”- Age: per-minute data past 35 days and hourly data past 400 days expire on their own. Your plan sets how far back charts can query (15 days on Lite, up to a year), which is a query window, not deletion — see the limits answer in the FAQ.
- Removing a server takes the server and its records out of your account immediately, with no undo, and revokes its API key. Its metric history is no longer reachable from the dashboard but is not purged on the spot — it ages out on the schedule above. The confirmation and its consequences are covered in Update or uninstall the agent.
- A server that is merely offline keeps its history: data already reported stays until it ages out on the schedule above, so a decommissioned-but-not-removed server’s charts remain readable for weeks.
There is no self-service account deletion yet — removing your servers takes them out of your account, but the account itself currently stays and stored metrics age out rather than being purged. To have everything deleted, email hello@monitorable.io.