DevOps Monitoring for Teams Responsible for Production

Host metrics, service checks and alert rules your on-call can act on, from one hosted dashboard.

  • One-command Linux agent
  • Checks every 60 seconds
  • 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

DevOps monitoring tools in one place

Bring host health, service checks and scheduled jobs into one hosted view your on-call already knows.

Linux host metrics

CPU, memory, 1-minute load, filesystem use, network receive and disk read.

Linux hostsIllustrative data
  • web-fra-01online
  • db-ams-02offline
  • cron-lon-01online

Ping and port checks

Ping and TCP checks from multiple locations every 60 seconds.

Host and port18msIllustrative data

Website and SSL checks

HTTP status, keyword, response time and certificate expiry.

Website responseIllustrative data
Status
200
Response
200 ms
Checked
1 min ago

Cron job monitoring

One-line check-ins for backups, reports and scheduled tasks.

Scheduled check-insIllustrative data

checked in 04:00

Server alerts

Thresholds with a duration, Up/Down grace periods and recovery messages.

Sustained thresholdIllustrative data
  • Disk > 90% for 10 mincritical

Separate host health from service health

The agent shows how the machine is doing: six host charts with history and the time each server last reported. External checks show what users reach: ping and TCP ports from multiple locations, plus HTTP status, keyword and response time for each endpoint. Read both side by side after a deploy to see whether the host or the service changed first. Server uptime adds Up/Down rules with a grace period you choose.

  • Six host charts with history
  • Service checks every 60 seconds
  • Up/Down rules with a grace period
Servers · statusIllustrative data
  • web-fra-01Ubuntu 22.04 · last seen 12 sec agoOnline
  • db-ams-02Debian 12 · last seen 3 min agoOffline
  • cron-lon-01AlmaLinux 9 · last seen 28 sec agoOnline
  • docker-nyc-03Ubuntu 24.04 · last seen 41 sec agoOnline
  • mail-sgp-01Rocky Linux 9 · last seen 1 min agoOnline

Keep scheduled work visible

Backups, reports and cleanup jobs run while nobody watches. Add one line that pings a unique check-in URL when each job finishes. If the check-in does not arrive, CloudStats sends an alert, and the host charts show what the server was doing at the time. Give every routine its own named check so the alert points to the right job. Read more about cron job monitoring.

  • One check per scheduled job
  • Missed-run alerts
  • Host context beside each job
crontabIllustrative command
your-job.sh && curl <your check-in URL>

Runs the check-in only when your job succeeds. Your real check-in URL is shown in the app.

Route alerts to the people who act

Set a threshold with a duration so short spikes pass, then choose warning and critical levels. Send each rule by email, to a Discord channel or as JSON to your own webhook, and receive a recovery message when the condition clears. Review rules after incidents and keep the ones that led to action. See server alerts for rule options.

  • Thresholds with a duration
  • Email, Discord or webhook
  • Recovery notifications
Alert ruleIllustrative data
WhenCPU usage
Is above90%
For at least5 minutes
SeverityCritical
NotifyDiscord · #ops

Brief spike ignored. Sustained breach alerts.

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

DevOps monitoring FAQ

How does DevOps monitoring fit an existing workflow?

CloudStats adds a hosted view of host metrics, service checks and scheduled jobs beside the logs and deployment records your team already uses. Install the one-command agent on each Linux host, add checks for the endpoints that matter and send alerts to the channel your responders watch.

What should we check after connecting a host?

Open the server details and review the six host charts: CPU, memory, 1-minute load average, filesystem utilization, network receive rate and disk read rate. Watch a normal working period, then set thresholds with a duration so your alerts reflect sustained conditions. Add ping, TCP port and cron checks for the services running on that host.

Can notifications go to our existing team channels?

Yes. Send each alert by email, to a Discord channel or as a JSON payload to your own HTTPS webhook. Route warnings to a team channel and critical conditions to the people on duty, and receive a recovery message when the condition clears.

Is it free?

CloudStats has a Free plan at $0, with unlimited servers, 24-hour metric retention, email alerts and community support. See Pricing for the current published plan details.

Give your on-call one place to look

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.