In this post, we’ll show you how to monitor the status of your MongoDB servers using Studio 3T’s Server Status Charts feature.
The Server Status Charts show real-time updates of what’s happening on a MongoDB instance. This makes it easier to monitor particular things of interest on production, development, test, or local instances.
You can open a Server Status Charts tab by right-clicking on a connection (or database, or collection) and selecting Server Status Charts from the Server Info menu:
You can customize which charts are shown by clicking on Select Charts in the upper right hand side corner of the Server Status Charts tab:
For example, if we wanted to focus on Operation Counts, Current Connections and Current Network Traffic, we would select only those, and the charts will be laid out intelligently to accommodate them:
What the Chart Information Means
In this section, we’ll explain the information shown on each chart.
Note that the information displayed in the charts may be:
- Cumulative – where the charts show information since the start of a particular point until the present moment, e.g. all events of a particular type since the database started.
- Per Update Period – where the charts show information about a particular event that occurred during an update period, e.g. if we have the ‘Update frequency’ set to ‘2 sec’, then the chart will show all events of that particular type that occurred within 2 second periods.
- Point in Time – where the charts show information about a particular event as it was at the point in time that the server status was requested from the database.
The table below details each of the server status charts:
Point in Time
The number of the active client connections performing read and write operations.
Point in Time
The number of operations that are currently queued and waiting for the read or write lock.
Point in Time / Per Update Period
The number of incoming connections from clients to the database server.
‘In use’ and ‘Available’ report the point in time values, ‘Total created’ shows values per update period.
|Current Network Requests|
Per Update Period
The number of distinct requests that the server has received during the update period.
|Current Network Traffic|
Per Update Period
The number of bytes that reflects the amount of network traffic received by and sent from this database during the update period.
|Total Connections Created|
Count of all incoming connections created to the server. This number includes connections that have since closed.
|Total Network Requests|
The total number of distinct requests that the server has received.
|Total Network Traffic|
The total number of bytes that reflects the amount of network traffic received by and sent from this database.
More detailed information about the counters the chart data are based upon can be found in the MongoDB documentation.
That’s it for this post! We hope the Server Status Charts will help you monitor your MongoDB servers and instances a little more closely. Speaking of monitoring, feel free to also read up on Data Compare & Sync, which lets you compare MongoDB databases and collections, and Schema Explorer, which lets you discover your data’s schema.
Editor’s Note: This post was originally published in September 2016.