Linux hosts, clear resource graphs

Linux Server Monitoring for CPU, Memory, Disk and Network

CPU, memory, load, disk and network history for every Linux server, with alerts when a problem lasts.

  • Ubuntu, Debian, AlmaLinux, Rocky
  • One-line install
  • Free plan
CloudStats · serversIllustrative data
  • web-fra-0147.2%
  • db-ams-0281.6%
  • cron-lon-0112.9%
  • docker-nyc-0334.5%
CPU81.6%
Memory72.4%
Load (1 min)3.18
Filesystem58.3%
CPU above 90% for 5 min · Critical

Runs on

  • Ubuntu
  • Debian
  • CentOS
  • AlmaLinux
  • Rocky Linux
  • systemd-based Linux

What CloudStats monitors on Linux

Find the resource under pressure, then follow its history.

CPU usage and load

Read CPU alongside 1-minute load average to spot busy hosts and CPU-bound work.

CPU64%Illustrative data

Memory

Follow memory utilization and see when a deployment or growing workload starts consuming headroom.

Memory68%Illustrative data
68% used32% free

Filesystem space

Choose a filesystem and catch a filling mount before logs or uploads exhaust its remaining space.

FilesystemIllustrative data

87%

Above 85% warning

Disk reads

Review disk read rate and connect changes with backups, reports or other read-heavy work.

Disk read24.6MB/sIllustrative data

Network receive

Choose an interface and follow incoming traffic when a host receives more data than usual.

Network receive4.71MB/sIllustrative data

History and time ranges

Change the shared time range to compare the same period across all six host charts.

Metric historyIllustrative data
1h6h24h

Linux performance monitoring with history

Compare an incident with normal behaviour. Align the charts around a deployment or traffic change to see which resource moved first.

  • One time range across the host charts
  • Filesystem and interface selectors for a closer view
  • A clear baseline before the next change
CloudStats · serversIllustrative data
  • web-fra-0147.2%
  • db-ams-0281.6%
  • cron-lon-0112.9%
  • docker-nyc-0334.5%
CPU81.6%
Memory72.4%
Load (1 min)3.18
Filesystem58.3%
CPU above 90% for 5 min · Critical

How it works

  1. Install the agent

    Add a server in the app and run its personal one-line command on that host.

    bash
    $ curl -fsSL https://install.cloudstats.me/YOUR_ENROLLMENT_TOKEN | sudo bash

    Copy your personal command from Add Server in the app. Each token is single-use.

  2. Review the charts

    Open CPU, memory, load, filesystem, disk read and network receive history together.

    CloudStats · serversIllustrative data
    CPU81.6%
    Memory72.4%
    Load (1 min)3.18
    Filesystem58.3%
    CPU above 90% for 5 min · Critical
  3. Set thresholds

    Choose a resource threshold, a duration and the channel that should receive the notification.

    Alert ruleIllustrative data
    WhenCPU usage
    Is above90%
    For at least5 minutes
    SeverityCritical
    NotifyDiscord · #ops

    Brief spike ignored. Sustained breach alerts.

Linux system monitoring vs. top, htop and Nagios

Compare live inspection, hosted history and a self-managed stack.

DimensionCloudStatstop & htopNagios
HistoryHost charts over timeLive terminal viewConfigured with your monitoring stack
AlertsThreshold plus durationNoConfigured checks and notifications
SetupPer-server install commandRun on the hostInstall and configure the stack
Many servers in one viewYesOne host per sessionConfigured host views
MaintenanceHosted serviceHost packagesSelf-managed stack and plugins

Alerts before users notice

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.

  • Threshold plus duration
  • Email, Discord or webhook
Illustrative data
Email09:41

db-ams-02 · CPU above 85% for 5 min

Discord09:38

web-fra-01 · filesystem / at 91.4%

Webhook09:17
{"event":"alert.resolved","server":"db-ams-02"}

Loved by sysadmins and developers

4.7 / 5 on Capterra · 62 reviewsRead all reviews
Easiest to use monitoring I have ever used.
Robert K.VoIP Support Manager · TelecommunicationsSep 2018via Capterra
Server Resource monitoring done well
Erwin W.Policy adviser, IT · Marketing and AdvertisingSep 2018via Capterra
Best Budget Solution For server Monitoring
Ganesh V.Founder · Media ProductionOct 2018via Capterra

FAQ

Linux server monitoring FAQ

What is Linux server monitoring?

Linux server monitoring brings host measurements together so you can follow resource use and investigate changes. Linux system monitoring connects CPU, memory, filesystem, disk and network readings with the workload they support. Build a baseline, compare an incident with normal behaviour, and choose alert thresholds that give your team a clear reason to act.

How do I monitor CPU and memory usage on a Linux server?

Add the host in the app and copy its personal install command. Run it on that server, then open the server details. CPU usage monitoring and memory graphs show resource pressure over your selected time range. Read load alongside CPU, compare changes with deployments, and set a threshold with a duration for sustained problems.

Does the agent affect server performance?

CloudStats uses a lightweight agent that sends host measurements to your dashboard. Watch its effect in the same CPU and memory charts after install. The graphs help you plan headroom for applications, backups and deployments without opening an SSH session for every review.

Is there a free plan?

Yes. The Free plan costs $0 per month and includes unlimited servers, 24-hour metric retention, email alerts and community support. Start with the hosts you run, review their graphs and create email rules for sustained problems. The Pricing page lists the plan details so you can choose the right fit for your team.

Which Linux distributions are supported?

CloudStats supports Ubuntu, Debian, CentOS, AlmaLinux, Rocky Linux and most systemd-based Linux distributions. Generate the install command for each server from Add Server in the app, then run that command on the intended host. The same host charts help you review resource use across machines running different distributions.

How long is metric history kept?

The Free plan keeps metric history for 24 hours. Select a time range in the server details to review the measurements available for that host. Use recent history to compare a busy period with quieter operation and follow a resource change through time. See pricing for the current plan details.

Start Linux server monitoring with a clear baseline

Connect your hosts and set your first duration-based alert.

bash
$ curl -fsSL https://install.cloudstats.me/YOUR_ENROLLMENT_TOKEN | sudo bash

Copy your personal command from Add Server in the app. Each token is single-use.