Node monitoring tracks the resource usage of each node in an ApsaraDB for MongoDB instance, including CPU usage, memory usage, IOPS, and more. Use it to investigate alerts and identify which nodes are behaving abnormally.
Limitations
Monitoring data is retained for 30 days. Data older than 30 days is unavailable.
If you receive an alert, such as a notification that CPU usage exceeds 80%, you can investigate by viewing the instance's monitoring data and filtering by node to identify abnormalities.
IOPS Usage and IOPS Usage (%) are not available for the following instance types and always display as 0 on the Monitoring Data page. The value 0 does not reflect actual IOPS usage.
Standalone instances
Replica set instances running MongoDB 4.2 with cloud disks
Sharded cluster instances running MongoDB 4.2 with cloud disks
View node monitoring data
Go to the MongoDB Replica Set Instances or MongoDB Sharded Cluster Instances page. In the top navigation bar, select a resource group and region, then click the ID of the target instance.Go to the MongoDB Replica Set Instances or MongoDB Sharded Cluster Instances page. In the top navigation bar, select a resource group and region, and then click the ID of the target instance.
In the left navigation pane, click Monitoring Data.
Click the Node Monitoring tab.
Select the node to view. The available node types depend on your instance type:
Replica set instances
Select a Primary, Secondary, or Read-only node. If you select a role without specifying a node, the graph shows the average metric values across all nodes with that role.
Sharded cluster instances
Select a Mongos, shard, or Configserver (CS) node. For shard nodes, you can then select a Primary, Secondary, or Read-only node. If you select a role without specifying a node, the graph shows the average metric values across all nodes with that role.
Standalone instances
Standalone instances display only the Primary node's monitoring data.
To change the time range, click the time range selector in the upper-right corner of the page.
To change the collection granularity, click the granularity selector in the upper-left corner of the monitoring graph.
Hover over any data point on a metric's graph to view details for that specific time.
For descriptions of all available metrics, see Metric descriptions.
Collection granularity
Collection granularity is the time interval between data points. ApsaraDB for MongoDB supports the following granularities: 5 seconds, 30 seconds, 1 minute, 10 minutes, 30 minutes, 1 hour, and 1 day.
The available granularities depend on the selected time range:
| Monitoring time range | Minimum granularity | Maximum granularity |
|---|---|---|
| >= 1 minute and <= 10 minutes | 5 seconds | 1 minute |
| > 10 minutes and <= 30 minutes | 5 seconds | 10 minutes |
| > 30 minutes and <= 1 hour | 5 seconds | 30 minutes |
| > 1 hour and <= 1 day | 1 minute | 1 hour |
| > 1 day and <= 7 days | 30 minutes | 1 day |
| > 7 days and <= 30 days | 1 day | 1 day |
For example, viewing a 1-day period with 1-minute granularity produces 1,440 data points.
If the selected time range is shorter than two granularity intervals, the graph shows only one data point and cannot form a curve. Select a longer time range or a finer granularity.