mongo-monitor CLI is a lean and simple tool to check the status of a MongoDB server or cluster. The code is on GitHub:
Here's how it looks in action:
In this animation I am monitoring a simple sharded cluster, and running some example maintenance operations, adding a node to a replicaset, stepping down a primary and shutting down a replicaset node.
A simple CLI which shows the status in real-time can be very useful to keep open when performing admin, letting you see how your changes affect the cluster as you work on it.
Installing the CLI
The CLI is installed with
npm install -g mongo-monitor-cli
Connecting to a Cluster
Connect to a cluster by providing a connection string. The tool uses
mongo-connection-string to parse the connection string, so you can be flexible with the input:
# Connect to a local instance mongo-monitor localhost:27107 # Connect to a remote replicaset, authenticated mongo-monitor admin:P@sswrd@mdbnode1,mdbnode2,mdbnode3?replicaSet=rs
Once a connection is established, the tool will periodically check the status of the cluster. If the cluster is sharded, it will also inspect each individual replicaset.
Here's the kind of output you might get from a replicaset:
The name of the replicaset is shown, along with each member. The status of each member is also shown, updating automatically every second.
This is convenient when administering replicasets, stepping down a master, adding or removing nodes and so on.
Sharded Cluster Status
When connecting to a sharded cluster, you will get output like this:
Each shard is shown, along with the details of the replicaset which make it up.
Keeping a view like this open is useful when administering sharded clusters, adding or removing shards, desharding, updating the replicasets which make up shards and so on.
If you like the tool, check out the code and feel free to make pull requests with additions! There are a few issues on the project already, and there are all sorts of features I'd love to add but haven't had the time, such as:
- Being able to see the lag for replicaset members, to see if secondaries are falling behind
- Being able to perform replicaset operations directly from the tool
- Showing the priorities of nodes if they are not the default
All ideas are welcome, let me know in the comments or repo, and share the tool if you find it useful!