This topic describes the monitoring items and metrics supported by the basic monitoring, advanced monitoring, and performance trends features of ApsaraDB for MongoDB.
Basic monitoring
The monitoring items vary based on the instance architecture. The monitoring items displayed in the ApsaraDB for MongoDB console shall prevail.
Instance architecture | Monitoring item | Metric and description |
| CPU utilization | cpu_usage: the CPU utilization of the instance. |
Memory usage | mem_usage: the memory usage of the instance. | |
Used disk space | The total disk space occupied by the instance. Related metrics:
| |
cursors | The number of cursors used by the instance. Related metrics:
| |
Read and write queue length | The total number of operations queued waiting for a global lock. Related metrics:
| |
Number of WiredTiger transactions | The number of and the available number of concurrent read and write transactions allowed into the WiredTiger storage engine. Related metrics:
| |
I/O latency | iocheck_cost: indicates how fast the current I/O system responds. Note This metric is supported only for standalone instances and replica set instances that run MongoDB 4.0 or earlier. | |
WiredTiger | The cache metrics of the WiredTiger engine used by the instance. Related metrics:
| |
| Disk usage | disk_usage: the proportion of the total disk space occupied by the instance to the maximum disk space available. |
QPS | The queries per second (QPS) of the instance. Related metrics:
| |
Connections | The number of connections to the instance. Related metrics:
| |
Network traffic | The network traffic of the instance. Related metrics:
| |
| IOPS usage | The IOPS usage of the instance. Related metrics:
Note The IOPS usage and IOPS utilization of a replica set or sharded cluster instance that runs MongoDB 4.2 and uses cloud disks cannot be queried. |
IOPS utilization | iops_usage: the proportion of the IOPS used by the instance to the maximum available IOPS. Note The IOPS usage and IOPS utilization of a replica set or sharded cluster instance that runs MongoDB 4.2 and uses cloud disks cannot be queried. | |
Primary/secondary latency | repl_lag: the latency in data synchronization between the primary and secondary nodes of the instance. Note The latency between the primary and secondary nodes of a replica set instance and the latency between the shard and Configserver nodes of a sharded cluster instance can be -2 to 2 seconds. This is because the heartbeat interval between replica set instances is 2 seconds. | |
Serverless instance | Number of requests | sl_qps: the number of requests per second. |
Advanced monitoring
The advanced monitoring feature is supported only by standalone, replica set, and sharded cluster instances.
The monitoring items vary based on the instance architecture. The monitoring items displayed in the ApsaraDB for MongoDB console shall prevail.
Instance architecture | Monitoring item | Metric and description |
| CPU utilization | cpu_usage: the CPU utilization of the instance. |
Memory usage | mem_usage: the memory usage of the instance. | |
Used disk space | The total disk space occupied by the instance. Related metrics:
| |
Connection utilization | conn_usage: the proportion of the current connections to the maximum connections. | |
cursors | The number of cursors used by the instance. Related metrics:
| |
Read and write queue length | The total number of operations queued waiting for a global lock. Related metrics:
| |
Average response time | avgRT: the average response time of the instance. | |
Number of WiredTiger transactions | The number of and the available number of concurrent read and write transactions allowed into the WiredTiger storage engine. Related metrics:
| |
I/O latency | iocheck_cost: indicates how fast the current I/O system responds. | |
WiredTigerCache usage | The cache usage of the WiredTiger engine for the instance. Related metrics:
| |
Number of affected documents | The number of documents of the instance. Related metrics:
| |
Operation details | The details of the operations performed on the instance. Related metrics:
| |
Number of indexes and documents that are queried and scanned | The number of indexes and documents that are queried and scanned. Related metrics:
| |
TTL | The TTL operation performed on the instance. Related metrics:
| |
| Disk usage | disk_usage: the proportion of the total disk space occupied by the instance to the maximum disk space available. Note The metric is not supported for serverless instances. |
QPS | The queries per second (QPS) of the instance. Related metrics:
Note The metric is not supported for serverless instances. | |
Connections | The number of connections to the instance. Related metric:
Note The metric is not supported for serverless instances. | |
Network traffic | The network traffic of the instance. Related metrics:
Note The metric is not supported for serverless instances. | |
| IOPS usage | The IOPS usage of the instance. Related metrics:
Note The IOPS usage and IOPS utilization of a replica set or sharded cluster instance that runs MongoDB 4.2 and uses cloud disks cannot be queried. |
IOPS utilization | iops_usage: the proportion of the IOPS used by the instance to the maximum available IOPS. Note The IOPS usage and IOPS utilization of a replica set or sharded cluster instance that runs MongoDB 4.2 and uses cloud disks cannot be queried. | |
Primary/secondary latency | repl_lag: the latency in data synchronization between the primary and secondary nodes of the instance. Note The latency between the primary and secondary nodes of a replica set instance and the latency between the shard and Configserver nodes of a sharded cluster instance can be -2 to 2 seconds. This is because the heartbeat interval between replica set instances is 2 seconds. | |
Sharded cluster instance | Total QPS of shard nodes in a sharded cluster instance | Total QPS of shard nodes in the instance. Related metrics:
|
Total QPS of mongos nodes in a sharded cluster instance | Total QPS of mongos nodes in the instance. Related metrics:
| |
moveChunk | The number of moveChunk operations performed on the current node that serves as the source or destination node. Related metrics:
|
Performance trends
The monitoring items vary based on the instance architecture. The monitoring items displayed in the ApsaraDB for MongoDB console shall prevail.
Instance architecture | Monitoring item | Metric and description |
| CPU utilization | mongodb.cpu_usage: the CPU utilization of the instance. |
Memory usage | mongodb.mem_usage: the memory usage of the instance. | |
Used disk space | The performance trends of the disk space used by the instance. Related metrics:
| |
cursors | The performance trends of cursors of the instance. Related metrics:
| |
Number of WiredTiger transactions | The performance trends of read and write requests and available concurrent requests. Related metrics:
Note These metrics are supported only for replica set instances of the standard edition. | |
WiredTiger | The performance trends of the cache metrics of the WiredTiger engine used by the instance. Related metrics:
Note These metrics are supported only for replica set instances of the standard edition. | |
| Disk usage | mongodb.disk_usage: the disk usage of the instance. |
QPS | The performance trends of the QPS of the instance. Related metrics:
| |
Connections | mongodb.connections.current: the total number of connections to the instance. | |
Network traffic | The performance trends of the network traffic of the instance. Related metrics:
| |
| IOPS usage | The performance trends of the IOPS usage of the instance. Related metrics:
|
IOPS utilization | mongodb.iops_usage: the IOPS utilization of the instance. Note The IOPS usage and IOPS utilization of a replica set or sharded cluster instance that runs MongoDB 4.2 and uses cloud disks cannot be queried. | |
Replica set instance | GlobalLock | Th performance trends of a global lock of the instance. Related metrics:
|