You don’t need a full observability stack to keep a few servers healthy — just the handful of signals that actually predict trouble, and what they mean.
Enterprise observability platforms assume you have a team to run them. If you’re keeping a handful of production servers alive without a dedicated SRE, most of that machinery is overkill — dashboards you never open, alerts you learn to ignore. What you actually need is to watch a small number of high-signal things and know what to do when one of them moves.
The signals that predict real trouble
- Disk headroom + trend: not just “85% full,” but “filling — full in ~3 days.” A full disk takes everything down.
- Memory pressure + swap: once you’re paging to disk, every process on the box gets slow. Watch for the leak, not just the level.
- Load relative to cores: load 8 on an 8-core box is saturated; the same number on a 2-core box is an emergency.
- Error rate on your web tier: a rising 5xx rate is the earliest sign something broke, often before users complain.
- Service liveness: is each thing that should be running actually up — or crash-looping? (And if you auto-restart it, do it safely.)
- Certificate + domain expiry: boring, silent, and a guaranteed outage if missed.
Levels are lagging indicators. Trends are leading ones.
A threshold alarm (“disk > 90%”) tells you you’re already in trouble. The more useful question is “where is this heading, and when will it become a problem?” A disk climbing 2% a day is worth a calm ticket today; the same disk at 90% and flat may be fine for months. Watch the slope, not just the value — and, ideally, learn what’s normal for each server so you can tell a real anomaly from a nightly backup.
The part most tools skip: what to do
Knowing a disk is filling is only half the job. The other half — find what’s eating the space, safely reclaim it, and make sure it doesn’t recur (we walk the diagnosis order in Why is my Linux server slow?) — is where a good ops engineer earns their keep, and where most monitoring tools shrug. That gap is exactly why we built Opservo: it watches the signals above, forecasts the ones that are trending wrong, explains what’s happening in plain English, and can run the fix with you. For a small team, that’s the difference between monitoring and actually being covered.
Originally published on the Opservo blog — Opservo is the AI ops engineer for teams without an SRE. Free for 2 servers → https://getopservo.com/welcome
Top comments (0)