Operations

Monitoring and Alerts

Host metrics up to 90 days, app traffic, alert rules and incidents.

Agents send host metrics every 15 seconds. The control plane keeps every sample for 7 days and hourly averages and peaks for 90 days, charts them per server and across the fleet, and evaluates alert rules every 30 seconds.

Metrics

CPU, memory and swap usage
Disk and inode usage on the root filesystem
Load average and network throughput
Services, containers and listening ports (inventory, every 60 seconds)

Server and fleet charts show the last hour, 24 hours, 7, 30 or 90 days; 7 days and longer are drawn from the hourly rollups.

Application traffic

Every site on VPSPilot's proxy writes an access log. Once a minute the agent counts requests per domain (total, 4xx, 5xx, bytes, and p50/p95 latency) and reports the counts, never the requests themselves. Each app's page shows its Traffic over 1 hour, 24 hours or 7 days, for requests through its domains (not its direct port). Counts are kept for 7 days.

Alert rules

VPSPilot ships with a rule for each of these. Change thresholds, durations and severities, or add more rules of the same kinds. Percentage thresholds stay below 100; certificate rules take days and backup rules hours (168 suits weekly backups), and those two are checked once rather than over a duration.

Rule	Target	Default	Severity
Agent offline	Server	No heartbeat for 5 min	critical
CPU sustained high	Server	≥ 90% for 15 min	warning
Memory pressure	Server	≥ 90% for 10 min	warning
Disk almost full	Server	≥ 85% for 30 min	warning
Inodes almost exhausted	Server	≥ 85% for 30 min	warning
Heavy swapping	Server	≥ 80% for 15 min (off by default)	info
Application down	Application	Not running for 2 min	critical
Certificate expiring	Domain	< 14 days left	warning
Backups stale or failing	Database	No good backup in 36 h	warning

How rules avoid noise

Metric rules average samples over the rule’s duration, so a single spike never alerts.
They resolve only once the value falls 3 points below the threshold, so values at the edge don’t flap.
There is at most one open alert per rule and target.

Alert states

State	Meaning
pending	The condition is true but hasn't held for the full duration yet.
firing	The condition held. Notifications go out.
acknowledged	Someone is on it. It stays open until the condition clears.
resolved	The condition cleared.

Firing and resolved alerts appear in every admin’s inbox, are emailed to those with alert emails on, and go to any alert channels (Slack, Telegram, webhook) that subscribe to them. See Notifications and Audit.