CPU usage and load
Read CPU alongside 1-minute load average to spot busy hosts and CPU-bound work.
Linux hosts, clear resource graphs
CPU, memory, load, disk and network history for every Linux server, with alerts when a problem lasts.
Runs on
Find the resource under pressure, then follow its history.
Read CPU alongside 1-minute load average to spot busy hosts and CPU-bound work.
Follow memory utilization and see when a deployment or growing workload starts consuming headroom.
Choose a filesystem and catch a filling mount before logs or uploads exhaust its remaining space.
87%
Above 85% warning
Review disk read rate and connect changes with backups, reports or other read-heavy work.
Choose an interface and follow incoming traffic when a host receives more data than usual.
Change the shared time range to compare the same period across all six host charts.
Compare an incident with normal behaviour. Align the charts around a deployment or traffic change to see which resource moved first.
Add a server in the app and run its personal one-line command on that host.
$ curl -fsSL https://install.cloudstats.me/YOUR_ENROLLMENT_TOKEN | sudo bashCopy your personal command from Add Server in the app. Each token is single-use.
Open CPU, memory, load, filesystem, disk read and network receive history together.
Choose a resource threshold, a duration and the channel that should receive the notification.
Brief spike ignored. Sustained breach alerts.
Compare live inspection, hosted history and a self-managed stack.
| Dimension | CloudStats | top & htop | Nagios |
|---|---|---|---|
| History | Host charts over time | Live terminal view | Configured with your monitoring stack |
| Alerts | Threshold plus duration | No | Configured checks and notifications |
| Setup | Per-server install command | Run on the host | Install and configure the stack |
| Many servers in one view | Yes | One host per session | Configured host views |
| Maintenance | Hosted service | Host packages | Self-managed stack and plugins |
Set a threshold and a duration so short spikes stay quiet. Route sustained pressure to email, Discord or webhook and give your team a clear starting point.
db-ams-02 · CPU above 85% for 5 min
web-fra-01 · filesystem / at 91.4%
{"event":"alert.resolved","server":"db-ams-02"}Easiest to use monitoring I have ever used.
Server Resource monitoring done well
Best Budget Solution For server Monitoring
FAQ
Connect your hosts and set your first duration-based alert.
$ curl -fsSL https://install.cloudstats.me/YOUR_ENROLLMENT_TOKEN | sudo bashCopy your personal command from Add Server in the app. Each token is single-use.