Skip to content

Linux Server Alerts

Know when a server needs you. Even with CtrlOps closed.

CtrlOps watches each Linux server for high CPU, a filling disk, a stopped service, a site going down, an expiring certificate or an SSH brute force, and messages your Slack, Telegram or webhook channel when one trips. Every alert runs on the server as a cron job, so it reaches you with the app closed. No agent to install.

Download for MacDownload for Windows

14-day free trial, no credit card required.

14 ready-made alerts, each with a limit you set. The Free plan includes 1 active alert per server, and the 14-day trial has no limit.

What do you want to hear about?

Example: Switch it on, set the limit, pick a channel. The check runs on the server, so the message comes even with CtrlOps closed, and another when CPU is back under the limit.

Switch it on, set the limit, pick a channel. The check runs on the server, so the message comes even with CtrlOps closed, and another when CPU is back under the limit. Example server and channel. Alerts run on your server as cron jobs, as the SSH user you connect with.

Why switch

How do you hear about problems today? One toggle per alert, no agent.

Pick how you watch your servers today, and see what changes in CtrlOps.

Today · A script or Monit

14checks to write, schedule and wire to Slack, on every server

  • One script per check: CPU, disk, services, SSL and more
  • A crontab line or a Monit file for each, on each server
  • It repeats every run and never says when it’s fixed

“I also like to set up a simple Monit configuration to alert me about high cpu usage or when the disk space is about to run out. … I’ve configured Monit to post them to my Slack team of 1.” Hacker News, 2016 (opens in a new tab)

With CtrlOps

1toggle per alert, with the limit and channel set in a form

  • 14 checks ready, from high CPU to SSH brute force
  • Installed on the server as a cron job for you
  • Bad checks in a row keep a spike quiet; CPU sends a recovery message

The alerts

14 alerts, ready to switch on. Set the limit, or keep the default.

Grouped the way the Alerts tab groups them, with the default each one starts at and how often the server runs it. Most can be added more than once, at another limit or for another service, site or disk.

  • System resources

    4
    • High CPU usage

      CPU stays above 85% for about 10 minutes. Includes the top processes.

      Default 85%Every 5 minRecovery message

    • High memory usage

      Memory stays above 90% for about 10 minutes. Includes the biggest processes.

      Default 90%Every 5 min

    • Swap usage high

      Swap stays above 80%, the early sign that RAM has run out.

      Default 80%Every 5 min

    • Out-of-memory kill

      The kernel killed a process because memory ran out.

      Every 5 minNothing to setNeeds root

  • Storage

    3
    • Disk space low

      A filesystem goes above 85%. Includes the largest folders.

      Default 85%Every 30 min

    • Inodes running out

      Inodes go above 90%. New files fail even while disk space is free.

      Default 90%Hourly

    • Backup failed or late

      A backup fails or does not run on time. One recovery message when they are good again.

      Hourly

  • Services

    3
    • Service stopped

      A systemd service you name stops running. Can restart it for you.

      Default Your serviceEvery 2 min

    • Failed systemd services

      Any systemd unit enters the failed state.

      Every 15 minNothing to set

    • Server rebooted

      The server restarted, planned or not. One alert per boot.

      Every 5 minNothing to set

  • Website and SSL

    2
    • Website down

      A URL stops returning 200, after 2 retries.

      Default Your URLEvery 2 minRun from another server

    • SSL certificate expiring

      A certificate is 14, 7, 3 and 1 days from expiry, with a reminder at each.

      Default 14 daysDaily at 09:00

  • Security

    1
    • SSH brute force

      20 or more failed SSH logins between checks. Includes the top source IPs.

      Default 20 loginsEvery 10 min

  • Cron jobs

    1
    • Cron job fails

      One of your own cron jobs fails, times out, or prints a pattern you pick.

      Every run of the job

14 alerts in all. Need a check that isn’t here? Write it as a cron job that exits with an error when something’s wrong, then switch on Cron job fails for it. See Cron Jobs

Inside the tab

Everything around an alert, in the same tab.

Where the messages go, a second limit, a pause for planned work, a check of your own, and where to see what a check found.

Where messages go

Save a channel once, test it, use it on every server

Two limits

An early warning at 75%, an urgent one at 90%

Planned work

Pause an alert and keep its settings

A check of your own

Get an alert when any cron job fails

Website down

Watch a site from a different server

What a check found

Every alert shows in Cron Jobs with its runs

Reviews

What people say about watching their servers.

Alerts are new in CtrlOps, so these public reviews are about what they’re built on: problems caught early, no agent on the server, and not being the one person who has to watch.

Problems across several servers

The AI-assisted debug loop for Linux servers is something we've wanted at RetainSure for a while. Chasing down intermittent issues across multiple EC2 instances usually means a lot of context switching between logs, metrics, and SSH sessions.
Anand ThakkarCo-Founder and CTO at RetainSureProduct Hunt logo

Caught before an outage

the fact that i dont need to install any agent on my servers sold me immediately. got it running on our staging env and already caught 2 issues before they became outages. will be moving prod over soon
Srushti VasaniOn Product HuntProduct Hunt logo

Debugging a worker at 11pm

this is exactly what i wanted last week debugging my railway worker at 11pm honestly 😭
Damian ForzaniFounder, DataBridge (email infra)Product Hunt logo

Finding problems by hand

…As a developer I mostly focus on building features, but whenever a production issue showed up I'd SSH into servers, dig through logs, and manually find the problem - time-consuming.
Amit KhicharOn LinkedInLinkedIn logo

When the one person is away

Most developer teams I know are still managing servers the same way they did 10 years ago: a spreadsheet of IPs, a bunch of SSH tabs, and one person who "knows the servers" and becomes a single point of failure the moment they're unavailable.
Drijesh P.Engineering Manager at IBMLinkedIn logo

FAQ

Questions about Linux server alerts.

Can't find your answer? Join Discord

  • Open the server in CtrlOps, go to the Alerts tab and switch on High CPU usage. Set the CPU limit (85% by default) and how many bad checks in a row must pass before it alerts (2 by default), then pick a Slack, Telegram or webhook channel. The check runs every 5 minutes, so with the defaults you hear about it once CPU has stayed above the limit for about 10 minutes.

  • Yes. Each alert is installed on the server as a cron job, so the server runs the check and sends the message itself. Close CtrlOps, or close your laptop, and the alert still reaches you.

  • No. There’s no agent or daemon. Each alert is a check that cron runs on a schedule, set up over the SSH connection CtrlOps already has, and it shows in the Cron Jobs tab like any other job.

  • Slack, Telegram or a webhook. Channels are saved once on the Alert Channels tab of the Home screen and reused by every alert and cron job on every server, and Send test there confirms delivery before you rely on one. There’s no email channel; a webhook can forward to one. Set up a channel

  • One high reading is usually a spike, like a deploy or a backup doing its work. Bad checks in a row sets how many checks in a row must cross the limit before you’re told. Raise it to hear less, lower it to hear sooner, or pause the alert during planned work.

  • Yes. Click Add alert, pick the same alert again and set another limit, for example High CPU usage at 75% to Slack and at 90% to a phone on Telegram. The same works for a second service, site or disk.

  • No. An alert runs on the server you switched it on for and watches that server. To watch several servers, open each one in CtrlOps and switch on its alerts there.

  • Yes, through Cron Jobs. Write the check as a cron job, a command or saved script that exits with an error or prints a word you choose when something’s wrong, then switch on Cron job fails for it. Cron Jobs

  • No. An alert tells you a limit was crossed, not what CPU looked like last Tuesday, and there’s no on-call rotation, acknowledgement or escalation: the message goes to the channels you picked. For live CPU, memory and disk, open Infra Details. Infra Monitoring

  • The SSH user you connect with, shown next to the tab’s title. An alert that needs more access, such as Out-of-memory kill, is marked Needs root, and needs a root connection.

  • The Free plan includes 1 active alert per server. Personal removes the limit, at $9 a month or $349 once for Lifetime, and the 14-day trial needs no credit card. Live monitoring in Infra Details is on the Free plan. The Alerts docs walk through each step.

Know when a server needs you.

PuTTY
Termius
MobaXterm
WinSCP
SecureCRT
Royal TS
Warp
CtrlOps14 tools left
Webmin
aaPanel
RunCloud
Dokploy
IP spreadsheet
bash (2)
sticky notes

Switch on the alerts you want, pick a channel, and the checks run on the server from then on. The Free plan includes 1 per server, and the 14-day trial has no limit and no credit card.

Start instantly · No credit card · Cancel anytime

Your privacy preferences. We use product analytics to improve CtrlOps. Google measurement runs without analytics cookies. Live chat stays off until you allow it. Cookie policy