Server alerts by severity
Open 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.
- Topic
- A · Fleet and servers
- Order
- 05 / 06
- Points
- 06
- 01Three severity levelsCritical, warning and info in their own tabs, with a server filter down to one machine.
- 02How long it’s been openEach row says how long the alert has been open, so one waiting for days doesn’t sink to the bottom.
- 03Assign to an operatorAlerts are assigned to an operator, so two people don’t work the same problem.
- 04Ack is not deleteAcknowledging removes an alert from the open list without deleting it; the history stays.
- 05Cost on the scoreEach alert shows what it costs the health score: 4 points for a critical, 1.5 for a warning.
What it does.
With seven alerts open, you don’t debate which one comes first. Each states what it costs the health score, so the order is already set. The same alerts show on the server page, so you don’t go elsewhere to check what’s open on a machine. Assign an alert and the rest of the team can see it is taken, so two people no longer work the same problem separately.
Three severity levels, each in its own tab, plus a server filter to narrow down to one machine.
Acknowledging removes an alert from the open list without deleting it, so the history stays.
Assign an alert to an operator so two people don’t do the same job.
Each alert’s effect on the health score shows in the itemised list on the dashboard: 4 points for a critical, 1.5 for a warning.
Alerts also show in the server profile. No separate list is kept.
Each row shows how long the alert has been open, so one that has waited for days doesn’t get lost at the bottom of the list.
Fleet and servers
The number of servers changes; where you look doesn’t.
- A.01Details 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.05This page 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