Linux Server Health Score Calculator

Calculate a weighted overall server health score from load average, memory, disk usage and failed services.

Inputs

Load Average (1-minute)

CPU Cores

Memory Utilization%

Disk Utilization%

Failed Services

Count of systemd units in a failed state (systemctl --failed)

Server Health Score

93.8

Health Grade

Excellent

Load per Core

80.0%

Total Penalty Points

6.2

Step by step

Values used
Load Average (1-minute) = 3.20; CPU Cores = 4; Memory Utilization = 72 %; Disk Utilization = 68 %; Failed Services = 0
Load, memory and disk penalties
penalty = max(0, metric% − 70) × weight
Health score
health_score = 100 − (load_penalty + memory_penalty + disk_penalty + failed_services × 10)
Server Health Score
= 93.8
Health Grade
= Excellent
Load per Core
= 80.0
Total Penalty Points
= 6.2

How it works

This composite health score starts from a perfect 100 and subtracts weighted penalties for each metric that exceeds a healthy 70% comfort threshold: load average per core, memory utilization and disk utilization are penalized proportionally once past that threshold, while each failed systemd service (which typically signals an outright application or configuration problem rather than gradual resource pressure) subtracts a flat 10 points, reflecting that even one failed service is a concrete issue worth immediate attention rather than a gradual capacity concern.

Formulas

Load, memory and disk penalties

penalty = max(0, metric% − 70) × weight

m: metric percentage (load/core, memory, or disk)
w: metric-specific weight

Health score

health_score = 100 − (load_penalty + memory_penalty + disk_penalty + failed_services × 10)

f: count of failed services

Frequently Asked Questions

Why does memory get a higher penalty weight than load or disk?

Memory exhaustion tends to cause more abrupt and severe failures than CPU or disk pressure — once physical memory and swap are exhausted, the OOM killer starts terminating processes somewhat unpredictably, whereas high CPU load and disk usage typically degrade performance more gracefully before causing outright failures.

Why does a single failed service cost a flat 10 points regardless of severity?

A failed systemd unit represents a definite, binary problem (something is not running that should be) rather than a gradient of resource pressure, so it is modeled as a fixed penalty per occurrence rather than scaling with a percentage — multiple failed services compound linearly since each represents an independent concrete issue.

Is a health score of 100 always achievable or realistic?

Yes — a healthy, well-provisioned server sitting comfortably under the 70% thresholds on load, memory and disk with zero failed services scores a perfect 100 under this model, which is intentional: the score is designed so that normal, non-alarming operation reads as fully healthy rather than being artificially deflated.

You might also need

System Capacity Planner Service Availability Calculator Load Average Calculator