Replication & HA topology
A visual primary/replica topology graph with per-member health and lag, fleet-wide.
The topology graph
The Replication & HA view draws each primary as a node with connector lines fanning out to its replicas — colored by health and labelled with per-member replication lag — so a cluster's shape is readable at a glance. A collapsible "Member details" panel lists every member with its role, state, and lag, and an HA-health badge flags each cluster as healthy, degraded (a member down or lagging), or single-node with no failover target.
Read straight from each engine
Membership and lag come from the engine itself, not inference: PostgreSQL pg_stat_replication, MongoDB rs.status(), Redis INFO replication, MySQL/MariaDB SHOW REPLICAS / SHOW REPLICA STATUS, SQL Server Always On availability groups (sys.dm_hadr_* DMVs), and Oracle Data Guard (v$database / v$dataguard_config / v$dataguard_stats).
Why it matters
A lagging or unhealthy standby is one of the most common precursors to an outage or a failed failover. Surfacing the whole fleet's replication posture in one place — with the same visual language across very different engines — means a degraded cluster or a single point of failure is obvious before it bites.
Try it yourself
Open the console and put this into practice.