Monitoring & alerts
What the agent actually reports, and how to get notified when something's wrong.
What's collected
Pushed every 15 seconds by the agent, no configuration needed:
- CPU, memory, disk, network, load average — full time-series history (retention varies by plan, see Plans & billing)
- Uptime / online-offline status
- Top processes snapshot
- Per-partition disk usage
- Disk health / SMART status (Linux via
smartmontools, Windows viaGet-PhysicalDisk) - Docker containers, if Docker is detected on the box
- Network interfaces and listening ports
All of this is viewable live on the server's detail page, and pullable via the read-only API.
Alert rules
An alert rule watches one metric on one server and fires when a condition holds for a minimum duration:
| Metric | Notes |
|---|---|
offline | No metrics push received recently |
cpu / memory / disk | Threshold + condition (greater than / less than) + duration, e.g. "CPU > 90% for 5 min" |
process | A named process disappearing (or appearing) from the top-processes list |
backup_failed | The most recent backup run for this server ended in failure |
monitor_down | Any external monitor on this server (see below) reports down |
A short duration requirement debounces single-blip noise — a CPU rule set to "5 minutes" won't fire on a one-second spike.
Delivery channels
| Channel | Setup |
|---|---|
| Always available — no setup. Extra recipient emails can be added per rule. | |
| Telegram | Link your Telegram account from Settings; alerts arrive as bot messages. |
| Slack | Paste an incoming-webhook URL from Settings — one webhook covers your whole account. |
| Generic webhook | Set per alert rule — MonitorFree POSTs a JSON payload to any URL you provide when the rule fires. |
Incident timeline
Each time an alert condition transitions from OK → firing (and back), that's logged as an alert event with a timeline you can review later — useful for "when exactly did this start" during a postmortem. Team members can leave comments on an event for shared incident notes.