ApsaraDB for MongoDB provides the monitoring data feature to monitor the running status of nodes in an instance. You can view metrics such as the CPU utilization and memory usage of commonly used resources in the Monitoring Data module.

Precautions

  • When you receive an alert message from Alibaba Cloud, such as a message which indicates that the CPU utilization of your instance exceeds 80%, you can view monitoring data of the instance in the ApsaraDB for MongoDB console to troubleshoot the issue. You can filter the nodes of the instance to check the status of each node and locate the node where the issue occurs.
  • Monitoring data is retained for up to 30 days. You cannot view the monitoring data that was generated more than 30 days ago.

Sampling granularity

The monitoring data feature differs in the old and new ApsaraDB for MongoDB consoles. We recommend that you use the new ApsaraDB for MongoDB console to experience more features. The following section describes the architectures:
  • In the new ApsaraDB for MongoDB console, the instance sampling granularity of standalone instances is fixed at 60 seconds, and that of replica set instances and sharded cluster instances is fixed at 5 seconds.
  • In the old ApsaraDB for MongoDB console, the instance sampling granularity can be set to 1 second or 300 seconds. For more information, see Set collection frequency of monitoring data.
Note If an instance has a sampling granularity of 1 second or 300 seconds, the sampling granularity of the instance is reset in the old ApsaraDB for MongoDB console or the instance is created before the sampling granularity is changed to 60 seconds. For more information about the change of instance sampling granularity, see Notice on changing the monitoring data collection interval to 60 seconds as November 19, 2020.

Procedure

  1. Log on to the ApsaraDB for MongoDB console.
  2. In the upper-left corner of the page, select the resource group and the region of the target instance.
  3. In the left-side navigation pane, click Replica Set Instances or Sharded Cluster Instances.
  4. Find the target instance and click its ID.
  5. In the left-side navigation pane, click Monitoring Data.
  6. View monitoring data based on instance categories:
    • Standalone instances
      You can view the monitoring data of a primary node. Monitoring data of a standalone instance
    • Replica set instances
      In the upper-right corner of the page, you can select a primary, secondary, or read-only node to view the corresponding monitoring data. Monitoring data of a replica set instance
    • Sharded cluster instances
      In the upper-right corner of the page, you can select a mongos node that starts with s-, a shard node that starts with d-, or a Configserver node that starts with -cs to view the corresponding monitoring data. Monitoring data of a sharded cluster instance
      If a shard node is selected, you can select a primary, secondary, hidden, or read-only node to view the corresponding monitoring data. Monitoring data of a sharded cluster instance
  7. Click the time range picker in the upper-right corner to specify a time range.
    Note By default, the monitoring data of the last day is displayed. You can specify a period of time within the last 30 days to view the monitoring data of an instance.
  8. View monitoring information. You can move the pointer over a point in time of a metric to view the details of the instance metric at the point in time. For more information about the displayed metrics, see Metrics.
    Basic monitoring