"Health Score: 98" is the output of dozens of metrics, continuously collected, converted, and weighted. This post lays out exactly what WAP tracks — from the host, to the instance, to the replication chain, to the query layer — one category at a time.
Just 6 of them shown here · what WAP actually tracks goes far beyond this
The five categories below form the backbone of WAP's monitoring system — covering the full chain from hardware resources to application-level queries.
The physical foundation the cluster runs on — any resource running dry shows up directly in database performance.
The MongoDB process's own runtime state — a direct read on the database's current load and health.
Whether a replica set can fail over cleanly when something breaks depends entirely on this group of metrics staying healthy.
The metrics that ultimately decide whether users experience your database as "fast" or "slow."
Collecting these metrics is only step one — WAP converts them into a readable health score, fires an alert the moment one crosses the safe line, and attaches the relevant context right alongside it, so an investigation never has to start from zero.
From the host to the query layer, Whaleal Platform puts the full metrics chain somewhere you'll actually look — instead of scattered across a dozen dashboards nobody opens.