Monitoring Overview
See what every server is doing right now and what it did over the last year — live metrics, processes, services, disks, network, availability, alerts, and the activity trail behind every change.
Devpilot's monitoring answers the questions you actually ask about a server: Is it up? What is it doing? What changed? Will it run out? Who should know? It is built on the Devpilot agent installed on each server and shows up in two places: a workspace-wide Fleet view and a per-server Monitoring area.
What you can monitor
Fleet
Every server in the workspace on one page — status, CPU, memory, disk, network, open incidents — sorted by how stressed it is.
Server monitoring
Overview, processes, services and containers, disks, network, availability and alerts for one server, updating live.
Alerts
Rules that watch any metric, incidents with the context captured when they fired, and notifications to the people and channels you choose.
Activity logs
Who created, changed, deployed or deleted what, across the workspace.
Logs
Deployment hook output, webhook deliveries and login history.
Deployment failure patterns
Recurring deployment failures grouped by cause, with suggested fixes.
How data gets there
Every connected server runs the Devpilot agent. It samples the server locally and sends the samples to Devpilot — nothing on your server is exposed inbound.
| Devpilot agent (current) | Legacy agent | |
|---|---|---|
| Sample interval | every 15 seconds, shipped in one-minute batches | every 3 minutes |
| Collected | CPU (overall, per core, I/O wait, steal), memory and swap, every real filesystem with inode usage, disk throughput, network throughput and errors per interface, TCP connection states, the top processes by CPU and memory, systemd services, Docker containers, host facts (OS, kernel, pending updates, reboot required) | CPU, memory, disk usage, network counters |
| Heartbeat | every 30 seconds, independent of samples | with each sample |
| Offline resilience | samples are queued on the server and delivered when connectivity returns | samples during an outage are lost |
A server's Agent & host card on its monitoring page shows the agent version it is running. Reinstalling the agent from the server page updates it to the current one.
How long data is kept
| Resolution | Kept for | Used by |
|---|---|---|
| Raw samples | 3 days | short ranges (up to a few hours) |
| 5-minute averages, minimums, maximums and 95th percentiles | 90 days | ranges up to a few weeks |
| Hourly | about 13 months | long ranges and year-over-year comparison |
Charts choose the resolution automatically for the range you pick, so a 30-day view never has to load every raw sample.
Live updates
Monitoring pages stay connected to Devpilot. A new sample appears on the charts within a few seconds of the agent collecting it, the status strip flips the moment a server goes quiet or comes back, and a new incident shows up without a refresh. The Live pill at the top of a page tells you the connection is up; if it drops, the page falls back to refreshing every minute.
Availability, honestly measured
A server is online while its agent heartbeats. If the heartbeats stop, the server is marked quiet for a short grace period and then offline — that transition is recorded as an incident with a start time, an end time when it recovers, and a duration. Uptime percentages, the 90-day status strip and mean time to recovery are all derived from those recorded outages, not from a self-reported "I'm up" flag.
Permissions
Anyone who can view the workspace can see monitoring. Creating and editing alert rules, acknowledging or resolving incidents, and installing or reinstalling the agent require the ability to manage servers in the workspace.