This dashboard provides basic information about MongoDB instances.
Shows how many times a command is executed per second on average during the selected interval.
Look for peaks and drops and correlate them with other graphs.
Keep in mind the hard limit on the maximum number of connections set by your distribution.
Anything over 5,000 should be a concern, because the application may not close connections correctly.
Helps identify why connections are increasing. Shows active cursors compared to cursors being automatically killed after 10 minutes due to an application not closing the connection.
When used in combination with Command Operations, this graph can help identify write amplification. For example, when one
update command actually inserts or updates hundreds, thousands, or even millions of documents.
Any number of queued operations for long periods of time is an indication of possible issues. Find the cause and fix it before requests get stuck in the queue.
This is useful for write-heavy workloads to understand how long it takes to verify writes and how many concurrent writes are occurring.
Asserts are not important by themselves, but you can correlate spikes with other graphs.
Memory faults indicate that requests are processed from disk either because an index is missing or there is not enough memory for the data set. Consider increasing memory or sharding out.
- Page updated 2021-01-11