Server health monitoring dashboard
See every server in your fleet on one screen: disk, memory, load and traffic. A single health score sits at the top. Under it is the list of what pulled the score down, such as a server offline, a critical alert or a backup that didn’t run. You know where to look first.
- Topic
- A · Fleet and servers
- Order
- 01 / 06
- Points
- 05
- 01Health scoreStarts at 100. Offline −11, degraded −7, critical alert −4, failed job −2, late backup −1.5.
- 02Where the points wentEach line shows what it costs. Lines with no effect are not printed.
- 03Needs attentionPicked by rule: disk over 82%, load per core over 0.7, mail queue past 250.
- 0424-hour curve30-minute buckets; now, peak, average and trend called out.
- 05New accountOpen an account from here and land on it in the list.
What it does.
If the score reads 82, the same screen shows where the missing 18 points went. Click a line and you land on that server. Machines that are filling up, running hot or piling up mail get a list of their own, because in a busy fleet those are the ones that slip past you. Creating a hosting account is one click from here as well.
The health score starts at 100. Each finding subtracts its own weight: offline server 11, degraded server 7, critical alert 4, failed job 2, late backup 1.5.
The score is itemised on screen, so you see what each line costs. Lines with no effect are not printed.
Servers needing attention are picked by rule: bad status, disk over 82%, load per core over 0.7 or a mail queue past 250.
Requests per second and bandwidth cover 24 hours in 30-minute buckets. Current, peak, average and trend are shown separately.
Start a new account here and, once it is created, you land straight on it in the list.
Fleet and servers
The number of servers changes; where you look doesn’t.
- A.01This page Server health monitoring dashboardSee every server in your fleet on one screen: disk, memory, load and traffic. A single health score sits at the top. Under it is the list of what pulled the score down, such as a server offline, a critical alert or a backup that didn’t run. You know where to look first.
- A.02Details Connect cPanel, Plesk and DirectAdminAdding a server takes two steps: type its address, then pick the panel type. You don’t hand over a root password. A full-privilege API token works for cPanel/WHM and DirectAdmin, an admin key for Plesk, and an SSH key for a panel-less Linux server. The token is stored encrypted and never shown again.
- A.03Details Server profile: load, disk, memoryEverything about one server sits on a single page: hardware, operating system, panel version, running services, its accounts, open alerts and the last backup. If the panel version is behind the newest in your fleet, it is flagged at the top. You can open the terminal from here too.
- A.04Details Linux service managementSee every server’s services in one table. “Is httpd running everywhere?” takes a single row: how many servers have it, how many are up and how many aren’t monitored. Before you restart Apache/httpd or any other service, the panel tells you how many sites it will touch.
- A.05Details Server alerts by severityOpen server alerts sit in three tabs by severity, and a server filter shows what is open on one machine. You assign an alert to someone on the team, and everyone can see who is on it. An alert you acknowledge leaves the open list but stays in the record.
- A.06Details Background job queueLong-running background jobs such as migrations and version moves are tracked here. You see which step a job is on and how much is left, and its log opens inside the row. Restart a job that stalled, or cancel one you no longer need.
Connect your first server today.
Free for 14 days, no card needed. Create your account, add your first server with an API token or an SSH key, and the panel starts filling in a few minutes later.
No setup fee · Cancel anytime · EU-hosted