Linux server monitoring that installs in one line
The Statance agent is a small bash script that reads /proc and /sys directly — no Python, no Node, no compiled binary to trust. It works on any distribution with bash and curl, from a $4 VPS to a 128-core bare-metal box, and reports every 60 seconds.
What to monitor on Linux
- 01CPU busy % and load averageLoad above your core count means work is queueing; CPU % alone can hide I/O wait.
- 02Memory and swapSwap usage climbing while free memory hits zero is the earliest sign of the OOM killer.
- 03Disk usage per mountA full / or /var stops databases and log writers outright.
- 04Network throughput per interfaceSpot traffic spikes, runaway backups or a saturated uplink.
- 05Top processesSee which PID ate the CPU at 3am without needing to SSH in.
- 06CPU temperatureRead from /sys/class/thermal where the hardware exposes it.
Set it up
Create a free account
Your API key is on the dashboard after sign-up.
Run the installer as root
It installs the agent to /opt/statance-agent, writes /etc/statance-agent and creates a systemd service.
curl -fsSL https://statance.com/install.sh | sudo bash -s -- YOUR_API_KEYCheck it is running
The server appears in your dashboard within a minute.
systemctl status statance-agentAdd alert rules
Pick a metric, a threshold and how long it must last, then choose who gets notified.
Recommended alerts for Linux
- Server stopped reporting for 5 minutes (down)
- CPU above 90% for 10 minutes
- Memory used above 90% for 5 minutes
- Any disk above 85% used
- Load average above number of cores for 15 minutes
Send alerts to
Linux FAQ
Which Linux distributions are supported?
Any distribution with bash 3.2+, curl and a standard /proc filesystem: Ubuntu, Debian, RHEL, Rocky, Alma, CentOS, Fedora, Amazon Linux, Arch, Alpine (with bash installed), openSUSE and more.
How much overhead does the agent add?
It wakes once a minute, reads a handful of files under /proc and /sys, and sends one small HTTPS request. It runs as a small long-lived loop; CPU and memory use vary by host and enabled collectors; measure on your workload.
Does it need root?
The installer needs root to create the systemd service. The default systemd service runs as root. A restricted service account requires reviewing collector access and configuration-file permissions; some metrics may no longer be available.
How do I uninstall it?
Run: sudo systemctl disable --now statance-agent && sudo rm -rf /opt/statance-agent /etc/statance-agent /etc/systemd/system/statance-agent.service
Uptime monitoring with super powers.
Know what you install and what it can read.
Review the installer and agent before running them on a server. The Linux installer places the agent in /opt/statance-agent, writes its API key and server token to /etc/statance-agent with mode 600, and creates a systemd service on systems using systemd. That service has no explicit User= setting and therefore runs as root by default. OpenRC and fallback modes are also handled by the installer.
The script relies on Bash, curl and standard operating-system tools. Optional collectors depend on tools and permissions available on the host. Running as a less privileged user can reduce collection coverage and requires correctly securing and granting access to the configuration file. Do not assume every collector works unchanged after a privilege reduction.
Verify collection before enabling alerts.
systemctl status statance-agent
journalctl -u statance-agent --since "10 minutes ago"
# In Statance, confirm the expected host and recent CPU, memory and disk readings.Agent metrics are collected every 60 seconds. Compare the dashboard with local tools such as df -h and free -m before deciding thresholds. Resource use varies by enabled collectors and workload; no universal CPU or RAM benchmark is promised here.
Before removal, disable alerts for that host if appropriate. The agent reference documents service management and removal. Agent removal does not imply automatic deletion of retained monitoring data.
Add an independent uptime check so an apparently healthy agent is not your only availability signal.