How does BetterDB Monitor's cluster visibility feature work?

Cluster visibility renders topology graphs of the Valkey Cluster alongside CLUSTER SLOT-STATS heatmaps, showing per-slot CPU usage and key distribution across the cluster.

That lets an operator spot a hot slot or an imbalanced shard visually, instead of trying to infer a topology problem from downstream application symptoms like uneven latency.

Paired with per-thread CPU and I/O metrics, this gives visibility that plain Redis tooling simply can't offer, because CLUSTER SLOT-STATS and per-thread stats don't exist as commands on Redis at all – both are Valkey-exclusive, which is also why this exact heatmap can't be reproduced against a Redis cluster no matter how it's configured.

In practice, the topology graph is usually the first thing you look at during an incident to confirm shard layout hasn't shifted unexpectedly, and the SLOT-STATS heatmap is the follow-up view when latency looks uneven across the cluster but the topology itself looks fine – it tells you whether the imbalance is a hot slot rather than a node problem.