Know a server is in trouble before your users do.
SRVCheck watches your server fleet from one place: CPU, drive iowait, RAM and swap, every disk partition, every network interface, and mdadm RAID health. A small Go agent pushes metrics over HTTPS - nothing to poll, no ports to open. Set alert thresholds and get notified to E-mail, Pushover, Discord, Telegram, Slack, webhook, or phone/sms with Twilio. Works great for homelab monitoring!
One static binary, no dependencies · amd64 and arm64 · Any systemd Linux · Windows (limited)
curl -sSL https://srvcheck.com/install?token=YOUR_TOKEN | sudo bash
The command installs the agent binary, its config in /etc/sysmon-agent/ and a systemd unit.
Metrics show up on your dashboard within a minute - you get the exact command, token included,
the moment you add a server.
A look inside
The server list, the alert history and the notification channels.
What it watches
Everything below is collected by default. There is nothing to configure per metric.
CPU and iowait
Usage and iowait every 30 seconds, with load averages alongside and 1h to 30d graphs that keep short spikes visible.
CPU temperature
Package temperature read straight from the kernel's hwmon sysfs - no lm-sensors, no IPMI. Virtual machines simply report none.
RAM and swap
Used, cached and available memory, with swap pressure and swap in/out activity alongside, so a leak or thrashing is obvious before the OOM killer finds it.
Disk per partition
Every mount point tracked on its own - space and inode use - so a filling /var never hides behind a roomy /. Per-device throughput, IOPS and await included.
Network per interface
rx/tx for each physical NIC with its negotiated link speed, and exact traffic totals for whatever range you are looking at.
mdadm RAID
Array state watched continuously. A degraded or failed array alerts on the next report - no waiting out an averaging window.
Uptime and reboots
Uptime per host, and a distinct alert when a machine reboots - deliberately separate from "went offline".
Threshold alerts
Per-resource rules with an averaging window and a repeat interval, set once for the whole organization or overridden per server.
How it works
Sign up
Create an account and name your organization. Invite the rest of the team later - everyone shares the same servers, alert rules and history, with roles from owner down to read-only viewer.
Run one command
Add a server, copy its curl … | sudo bash line and run it as root on the box.
The agent authenticates with a per-server bearer token you can regenerate at any time.
Watch, and get told
Graphs from one hour to thirty days, a status dot per host, and threshold alerts to email, Pushover, Discord, Telegram, Slack, your own webhook, or phone/sms with Twilio. Mute a host with maintenance mode while you work on it.
Simple plans
Every plan monitors every metric. What changes is scale, history and channels.
Free
Start hereKeep watch of a handful of servers.
- 25 servers
- 5 team members
- 90 days of history
- Reports as often as every 1 min
- email, discord, pushover, webhook, slack, telegram, twilio
Pro
For small fleets that need real history and a team.
- 50 servers
- 10 team members
- 180 days of history
- Reports as often as every 1 min
- email, discord, pushover, webhook, slack, telegram, twilio
Ready to see your fleet?
Add your first server and have graphs inside five minutes.