Your server's page on the panel shows how it is doing: CPU, memory, disk, network, load and uptime, refreshed every few seconds.
What you see
Open Dashboard > your server. The Server health card shows:
- CPU: how busy the processor is, with the number of cores and the one-minute load average.
- Memory: used memory against the total.
- Disk: how full the disk with your code and databases is, and the free space left.
- Network in and out: your environment's traffic, per second.
- Up for: how long the server has been running since its last restart.
- System updates: how many updates the server's own operating system is waiting for, how many of them are security updates, and Restart needed when an installed update only takes effect after a restart.
- A chart of CPU and memory over the last 30 minutes, 24 hours or 30 days (hourly averages for the longer ranges).
The badge next to the title sums it up: Healthy, Busy when CPU, memory or disk is at 90% or more, Not reporting when reports have stopped (the server is off, or cannot reach rdev.cloud), and Waiting before the first report.
How often it updates
The server sends a report every 15 seconds by default. Choose another interval under Report every, from 5 seconds to 5 minutes; the server switches with its next report and the card refreshes at the same pace.
To stop reports altogether, choose Off. The server then sends no figures at all; it only checks every five minutes whether you turned reports back on. Alerts stop too.
Alerts
With Alerts on (the default), you are told when:
- the disk is 90% full or more;
- memory has stayed at 90% or more for five minutes;
- the server has sent no report for 10 minutes.
Disk and memory alerts go to your server's own notification channels (ntfy, Slack, email and the others you set up), sent by your server itself. A server that stopped reporting cannot send anything, so that alert is emailed to you by rdev.cloud, once per outage. Each kind of alert is sent at most once every six hours.
Is the server big enough?
When the server was short of memory or CPU for more than a fifth of the time over the last week, the card suggests a larger size, with a link to Get a server.
System updates
The installer turns on your distribution's automatic security updates (unattended-upgrades on Ubuntu and Debian, dnf-automatic on Rocky and AlmaLinux) and checks once a day for pending updates. Security updates install themselves; restart the server when the card says Restart needed (sudo reboot; your environment starts again on its own). Servers installed earlier get this with sudo rdev host update.
What is sent
Only the figures above: numbers, never file names, processes or content. Reports go from your server to rdev.cloud over HTTPS; the reports are deleted after 24 hours and their hourly averages after 30 days. Team members' own environments run on the same server, so only the main environment reports.
Server health needs rdev 0.2.0-beta.15 or later on the server; turning reports off, alerts and system updates need 0.2.0-beta.16. Update with sudo rdev update and sudo rdev host update.