Health Score
The Health Score is a single 0–100 number per server, rolled up across your fleet. It’s built to be honest about what Demerzel actually knows.
Factors and coverage
The score combines six factors, each scored 0–100. Each one also reports a coverage: how much evidence backs it, and how fresh it is.
| Factor | What it scores |
|---|---|
| Capacity | The fuller of disk and memory — the worst resource wins. |
| Updates | Pending updates, weighted heavily for security updates, plus whether a restart is required. |
| Security | Vulnerabilities that have a fix available, weighted by severity (critical, high, medium, low). |
| Exposure | Sensitive services (databases, admin ports) reachable from the internet with no host firewall. A firewall that is up, or nothing sensitive exposed, scores full marks. |
| Availability | How recently the server reported: full marks within five minutes, dropping as the silence grows. |
| Agent | Whether the agent runs the latest release; the further behind, the lower. |
Null is not zero. A factor with no evidence lowers coverage rather than scoring 0. A server Demerzel can’t see clearly is reported as low-coverage, never as falsely healthy.
Bands
| Band | Score | Meaning |
|---|---|---|
| Healthy | 90–100 | Nothing needs attention. |
| Warning | 75–89 | Worth a look soon. |
| Critical | below 75 | Needs attention now. |
The fleet score is coverage-weighted, so a well-observed server counts more than one you’ve barely started monitoring. Open any server to see the full per-factor breakdown.