Node monitoring (formerly basic monitoring)
Monitor the resource usage of each node in an ApsaraDB for MongoDB instance, including metrics such as CPU utilization and memory utilization.
Usage notes
-
If you receive an alert from Alibaba Cloud, such as CPU utilization exceeding 80%, view the instance monitoring data and filter by node to identify which node has the issue.
-
Monitoring data is retained for 30 days. Data older than 30 days cannot be viewed.
-
The IOPS Usage and IOPS utilization metrics are unavailable for standalone instances and for replica set or sharded cluster instances that run MongoDB 4.2 with cloud disks.
For these instances, the Monitoring Information page in the ApsaraDB for MongoDB console always displays 0 for the IOPS Usage and IOPS Usage metrics. This value does not reflect the actual IOPS data.
Collection granularity
ApsaraDB for MongoDB supports the following collection granularities, which determine the time interval between data points: 5 seconds, 30 seconds, 1 minute, 10 minutes, 30 minutes, 1 hour, and 1 day.
For example, if you set the time range to 1 day and the collection granularity to 1 minute, the monitoring chart consists of 1,440 data points.
The available collection granularities depend on the selected time range, as described in the following table.
|
Time range |
Minimum collection granularity |
Maximum collection granularity |
|
1 minute to 10 minutes |
5 seconds |
1 minute |
|
Greater than 10 minutes and less than or equal to 30 minutes |
5 seconds |
10 minutes |
|
Greater than 30 minutes and less than or equal to 1 hour |
5 seconds |
30 minutes |
|
Greater than 1 hour and less than or equal to 1 day |
1 minute |
1 hour |
|
Greater than 1 day and less than or equal to 7 days |
30 minutes |
1 day |
|
Greater than 7 days and less than or equal to 30 days |
1 day |
1 day |
If the time range is shorter than two collection granularity intervals, the chart displays a single data point instead of a line graph.
Procedure
-
Go to the Replica Set Instances, Sharded Cluster Instances, or Serverless Instances page, select a resource group and a region in the top navigation bar, and then click the target instance ID.
-
In the left-side navigation pane of the instance details page, click Monitoring Data.
-
Click the Node Monitoring tab.
-
Select a node based on the instance architecture to view its monitoring data.
Replica set
In the upper-left corner of the page, select a primary, secondary, or read-only node.
NoteIf you select a role without selecting a specific node, the monitoring charts display the average metric value across all nodes with that role.
Sharded cluster
In the upper-left corner of the page, select a mongos, shard, or ConfigServer node.
If you select a shard node, you can further select a primary, secondary, or read-only node.
NoteIf you select a role without selecting a specific node, the monitoring charts display the average metric value across all nodes with that role.
Standalone
You can directly view the monitoring data of the primary node.
Serverless
In the upper-right corner of the page, select a mongos ID to view the monitoring data for the corresponding node.
NoteServerless instances include two mongos nodes to ensure high availability.
-
Click the time range picker in the upper-right corner to change the time range as needed.
-
To change the collection granularity, click Collection Granularity in the upper-left corner of a monitoring chart.
-
View the monitoring data. Hover over a data point on a trend chart to see detailed metric information at that time.
For descriptions of monitoring items, see Monitoring items and metrics.