ApsaraDB for MongoDB provides node monitoring to view the resource status of each node in an instance, including common metrics like CPU and memory utilization.
Usage notes
-
When you receive an alert message from Alibaba Cloud, such as for CPU utilization exceeding 80%, investigate the issue by viewing the instance's monitoring data. You must filter by node to check for issues on individual nodes.
-
Monitoring data is retained for 30 days. You cannot view monitoring data that is older than 30 days.
-
Standalone instances, along with replica set and sharded cluster instances running MongoDB 4.2 with cloud disks, do not support IOPS usage or IOPS utilization.
Currently, for instances that use the preceding architecture, the IOPS Usage and IOPS Usage metrics on the Monitoring Information page of the console always show a value of 0. This value does not represent the actual IOPS monitoring data.
Collection granularity
ApsaraDB for MongoDB allows you to select a collection granularity, which is the time interval between data points. Supported granularities include 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 shown 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 only 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.
-
Based on the instance architecture, select a node to view its monitoring data.
Replica set
In the upper-left corner of the page, select a primary, secondary, or read-only node to view its monitoring data.
NoteIf you select a role but do not select a specific node, the monitoring charts display the average metric value for all nodes with that role.
Sharded cluster
In the upper-left corner of the page, select a mongos, shard, or ConfigServer node to view its monitoring data.
If you select a shard node, you can then select a primary, secondary, or read-only node to view its monitoring data.
NoteIf you select a role but do not select a specific node, the monitoring charts display the average metric value for 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.
-
As needed, click the time range picker in the upper-right corner of the page to change the time range.
-
To change the collection granularity, click Collection Granularity in the upper-left corner of a monitoring chart.
-
View the monitoring data. Hover the pointer over a point on a trend chart to see detailed information for that metric at that time.
For descriptions of each monitoring item, see Monitoring items and metrics.