Replica Set Fleet Dashboard
The Replica Set Fleet Dashboard gives you a single-pane view of every MongoDB replica set VisuaLeaf is connected to. Instead of jumping between connections, you see quorum status, member health, and oplog lag for every replica set in one grid — and drill into any one of them for deeper diagnostics.
The default layout is a dense table that shows every replica set at a glance. Each row is one replica set; each column is a summary metric so you can spot outliers without opening anything.
| Column | Description |
|---|---|
Name |
The replSetName from rs.status() |
Quorum |
Green / amber / red indicator based on voting-member majority |
Members |
Health chips for each member (PRIMARY, SECONDARY, ARBITER, etc.) |
Oplog Lag |
Highest secondary lag in seconds — sortable to surface the worst case |
Version |
MongoDB server version reported by each member |
Last Seen |
Time since the last successful heartbeat |
Switch to Card view from the toolbar for a more visual layout. Each card shows the replica set name, the quorum ring, member chips laid out around a topology dot, and a mini oplog-lag sparkline. Cards are useful when you have fewer than 20 replica sets and want to see topology at a glance.
Quorum is the most important signal on the fleet page. A replica set with quorum can accept writes; one without cannot. The indicator uses three colors:
When quorum turns red, VisuaLeaf shows a banner explaining why — for example, 2 of 3 voting members unreachable or PRIMARY stepped down, no eligible SECONDARY. Cross-reference with the Last Seen column to see whether members are truly down or the app-server is simply partitioned from them.
Each member appears as a colored chip labeled with its state. The chip color mirrors the member state code returned by rs.status().
| Chip | State | Meaning |
|---|---|---|
● PRIMARY |
1 | Accepting writes. Exactly one per set. |
● SECONDARY |
2 | Replicating from the primary, serving reads if readPreference allows. |
● ARBITER |
7 | Votes in elections but holds no data. |
● HIDDEN |
2 + hidden | Secondary excluded from client reads (typically for backup or analytics). |
● RECOVERING |
3 | Rolling back or resynchronizing. Not usable for reads yet. |
● DOWN |
8 | Not reachable by the current primary. |
Oplog lag is the difference between the primary's most recent oplog timestamp and each secondary's applied timestamp. The fleet page shows the worst secondary lag per set. Click the column to sort descending — this is the fastest way to find replication problems across dozens of sets.
Rows are color-tinted based on lag:
The Auto-refresh switch in the toolbar polls rs.status() and heartbeat data on a fixed interval:
5s — for active incident response. Use sparingly on large fleets to avoid heartbeat load.15s — a good default for day-to-day monitoring.60s — light polling for background awareness.Auto-refresh only re-fetches the summary. Detail panels refresh on demand so you never lose scroll position.
Clicking a row (or a card) opens the RS Monitor view for that replica set. From there you can see per-member metrics (heartbeat latency, applied ops/sec, storage stats), inspect election history, and jump straight to the Oplog Browser scoped to that set.
Any connection you add through the Connection Manager that targets a replica set is picked up automatically. To add one:
mongodb://host1:27017,host2:27017,host3:27017/?replicaSet=rs0.Use connection tags (e.g. prod, staging, region-us-east) to group replica sets on the fleet page. The Group by selector re-orders the grid by tag, which is much easier than scrolling a flat list of 40+ sets.
Download and start managing your MongoDB databases with ease.
Download Free Trial