# Disk-space alert threshold and acceptance worksheet

Source guide: https://happysysadm.com/monitoring-rmm/disk-space-monitoring-alerts/

Use one consistent capacity unit. Examples in the guide use GiB. Store completed records privately; hostnames, paths and operational details may be sensitive.

## Scope and measurements
- Service / environment:
- Host and stable volume identifier / mount path:
- Storage layer (guest, pool, datastore, repository):
- Service owner / responder:
- Observation time and time zone:
- Collection method and supported version:
- Expected volumes reconciled against discovery:
- Capacity and current free space:
- Free percentage:
- Operational reserve and reason:
- Representative net growth per day (normal / faster-growth case):
- Observation period and excluded one-off events:
- Known upcoming burst / restore / consolidation requirement:

## Decision
- Usable headroom = current free space minus reserve:
- Time to reserve = usable headroom / positive net growth:
- Zero/negative growth: forecast unavailable or not declining; retain absolute-space checks.
- Expansion/mitigation lead time:
- Contingency:
- Warning condition and recipient:
- Urgent condition and escalation:
- Absolute operational floor:
- AND/OR logic between conditions:
- Persistence window:
- Recovery condition / duration:
- Missing-data threshold and response:
- Documented exclusions and owner:

## Controlled acceptance check
Do not fill production storage to trigger an alert.

| Check | Result / timestamp / evidence | Owner / remaining action |
|---|---|---|
| Expected volume discovered | | |
| Fresh measurement and units verified | | |
| Warning rule evaluated using safe test | | |
| Urgent route and escalation verified | | |
| Notification received and acknowledged | | |
| Missing or stale measurement detected | | |
| Recovery condition verified | | |
| Temporary test changes removed | | |
| Application behaviour after approved change | | |

Next review trigger / date: