A good monitoring page should tell you "is everything okay" within three seconds, "what's wrong" within ten, and "why it's wrong" within a minute. This post breaks down exactly what WAP's real-time monitoring page does — from the overview, to drilling into detail, to side-by-side comparison, to looking back through history.
Open WAP's monitoring page and the first thing you see isn't a single chart — it's the state of the entire cluster. Every node's role, health, connections, and lag are all laid out at once. Most of the time, that one glance is enough to tell you "nothing needs attention right now."
When the overview flags a node that looks off, the next step is clicking into it — WAP expands that node's full set of detailed metrics: CPU, memory, disk I/O, network throughput, each laid out on its own, down to the second, instead of one vague percentage.
Drill from the overview down to a single node, every metric charted on its own.
Looking at one node's chart alone, it's hard to tell whether "42% CPU" is high or not. WAP's multi-dimensional comparison lays the same metric across multiple nodes, shards, or even multiple clusters side by side — an anomaly usually isn't a line suddenly spiking, it's a line suddenly looking different from all the others.
Cross-node, cross-shard, cross-cluster comparisons — spot the anomaly at a glance.
The worst thing in monitoring is finding out too late. Data on WAP's page refreshes every second, with no manual refresh button needed — the instant something breaks, the chart shows it immediately, instead of you discovering it ten minutes later on your own.
Health status refreshed every second, risk flagged before it escalates.
1 hour, 6 hours, 24 hours, 7 days — the monitoring page lets you freely switch the time window, putting the live view and historical charts in the same interface. Reconstructing an incident doesn't mean digging through logs anymore.
From overview to drill-down, from comparison to history — every one of these features exists for a single goal: making sure you know what happened before the business team does.