Server Monitoring

Know what's happening inside your servers — not just whether your site is up.

SiteVitals Server Monitoring gives you real-time visibility into the health of your Linux servers. CPU load, memory pressure, disk usage, load average, and running processes — all collected every minute and surfaced in a clean dashboard with alerting built in.

Uptime monitoring tells you when your site goes down. Server monitoring tells you why — and warns you before it happens.

How it works

You install a lightweight agent script on your server in under a minute. The agent collects system metrics every 60 seconds and pushes them to SiteVitals via a secure HTTPS API call. No open ports, no inbound firewall changes, no persistent daemon — the script runs, reports, and exits.

SiteVitals evaluates each check against your configured thresholds. When a metric breaches the warning or critical level and stays there for the configured duration, your alert channels fire — with escalation support so the right people get notified at the right time.

A server can be linked to one or more of your monitored sites, so server incidents appear on those sites' event timelines and alerts include which sites may be affected.

What gets monitored

Key features

• › One server, multiple sites — Link a single server to all the sites it hosts. Server incidents automatically appear on those sites' event timelines.
• › Configurable thresholds — Set your own warning and critical percentages per metric. Defaults are sensible out of the box — adjust when you know your server's normal behaviour.
• › Sustained breach detection — CPU and memory alerts only fire after a configurable sustained period (default: 5 minutes), preventing noise from momentary spikes.
• › Escalation channels — Configure multiple alert channels per server with different delays — notify the on-call developer after 5 minutes, the manager after 30.
• › 24-hour history charts — Click any metric card on the dashboard to see a Chart.js history view with 1h, 6h, 24h and 7-day ranges.
• › Systemd and cron support — The installer auto-detects whether your server uses systemd timers or traditional cron and configures the appropriate scheduler.
• › No open ports required — The agent pushes data outbound over HTTPS. You don't need to open any firewall ports or allow inbound connections.
• › Low overhead — The agent consumes under 0.3% CPU per run and approximately 1.5 MB of network traffic per day. It exits completely between runs.

Common questions