To view monitor metrics, click on host name of the chosen server.
As shown in the picture 4-5, monitor metric groups are at the left side menu including、「Favourite」,「Host Status」,「Utilization」,「Events」, 「Saturation」,「Throuhgput」,and「Performance」.
Click on the metric group, metric items will appear underneath.
Click on the metric items, the monitoring chart will display on right side of the page.
4-7 Monitor Metrics-1
Take Network metric as an example, MongoDB’s memory traffic is presented in line chart. X-axis specifies recording period and Y-axis shows the amount of traffic receiving/sending from database.
In addition, time scale can be set to adjust data recording frequency. As shown in picture 4-8 below, the time scale is 5 seconds, thurs at 13:27:17, one network traffic data is recorded and the next sampling point is at 13:27:22.Each time scale associates with a default time interval array display for simpler view setting.
Display time interval can also be modified to meet user’s monitoring requirements. If the interval is selected for 3 hours, then the chart will display data records in the last 3 hours.
4-8 Monitor Metric-2
4-9 Monitor Metric-3
Check the box beside the heart to display data sampling points.
Note: This function is only selectable between 50 to 300 Data sampling points. For 300 points and more, chart will only display by line chart. For 50 points and less, chart will only display by points.
Click on Auto to stop chart refreshing
Click on SI to display system of units
4-10 system of unit
Table 3 Metric List
||CPU usage rate
||CPU idle rate
||CPU wait for IO rate.
||MongoDB CPU usage rate
||Total memory of server
||Total MongoDB virtual memory used (Swap+Res)
||MongoDB resident memory used.
||MongoDB shared memory
||Percentage of MongoDB virtual memory used.
||Total Swap Memory of server
||Available Swap Memory
||Swap Memory used
||Size of MongoDB dbPath
||MongoDB storage used
||Available MongoDB dbPath size?
||Percentage of MongoDB storage used
||Number of user connection
||The number of cursors that MongoDB is maintaining for clients.
||The total number of cursors that have timed out since the server process started.
||The amount of mapped memory, in megabytes (MB), by the database.
||The amount of mapped memory, in megabytes (MB), including the memory used for journaling.
||The value of mem.resident is roughly equivalent to the amount of RAM, in megabytes (MB), currently used by the database process.
||It displays the quantity, in megabytes (MB), of virtual memory used by the mongod process.
|Journaled Size (V2.6)
||The amount of data in megabytes (MB) written to journal during the last journal group commit interval.
|WiredTiger Cache (V3.4)
||Size in byte of the data currently in cache.
||Maximum cache size.
||Size in bytes of the dirty data in the cache.
|WiredTiger Transactions (V3.4)
||Number of available read tickets remaining.
||Number of read tickets in use.
||Number of available write tickets remaining.
||Number of write tickets in use.
||The number of message assertions raised since the MongoDB process started.
||The number of regular assertions raised since the MongoDB process started.
||The number of 'user asserts' that have occurred since the last time the MongoDB process started.
||The number of warnings raised since the MongoDB process started.
||The total number of page faults.
||The number of operations that are currently queued and waiting for the read lock.
||The total number of operations queued waiting for the lock.
||The number of operations that are currently queued and waiting for the write lock.
|Journaled Lock (V2.6)
||The count of the commits that occurred while a write lock was held.
||The number of the active client connections performing read operations.
||The number of active client connections performing write operations.
||The number of bytes that reflects the amount of network traffic received by this database.
||The number of bytes that reflects the amount of network traffic sent from this database.
||The total number of commands issued to the database since the mongod instance last started.
||The total number of delete operations since the mongod instance last started.
||The total number of "getmore" operations since the mongod instance last started.
||The total number of insert operations received since the mongod instance last started.
||The total number of queries received since the mongod instance last started.
||The total number of update operations received since the mongod instance last started.
||Difference between the primary's oplog window and the replication lag of the secondary.
||Delay between a write operation on the primary and its copy to a secondary.
|Background Flush (V2.6)
||The amount of time, in milliseconds, that the last flush operation took to complete.
|Journaled Time (V2.6)
||The amount of time, in milliseconds, spent writing to data files after journaling.
||Accesses reports the number of times that operations have accessed indexes.
||The hits value reflects the number of times that an index has been accessed and mongod is able to return the index from memory.
||The misses value represents the number of times that an operation attempted to access an index that was not in memory.