ApsaraDB for MongoDB:Advanced monitoring

Prerequisites

• ARMS is activated for your instance. For more information about how to activate it, see Activate ARMS.

  Note

  For more information about ARMS, see What is ARMS?

• The instance is a standalone, replica set, or sharded cluster instance.

Usage notes

The IOPS Usage and IOPS Usage (%) metrics of the following instances cannot be displayed in the ApsaraDB for MongoDB console: standalone instances, replica set instances that run MongoDB 4.2 and use cloud disks, and sharded cluster instances that run MongoDB 4.2 and use cloud disks.

The IOPS Usage and IOPS Usage (%) metrics of the preceding instances are displayed as 0 on the Monitoring Data page in the console, which do not indicate the actual IOPS usage.

Billing rules

You are not charged for the use of the advanced monitoring feature.

Procedure

1. Go to the Replica Set Instances or Sharded Cluster Instances page. In the top navigation bar, select the region in which the instance resides and the resource group to which the instance belongs. Then, find the instance and click the ID of the instance.

2. In the left-side navigation pane of the instance details page, click Monitoring Data.

3. Click the Advanced Monitoring tab.

4. Select the role and corresponding nodes whose monitoring data you want to view based on the instance architecture.

   Replica set instance

   In the upper-left corner of the Advanced Monitoring tab, you can select the primary, secondary, or readonly role to view the monitoring data of a node corresponding to a role. The readonly role is displayed only when read-only nodes are added to the instance.

   Sharded cluster instance

   In the upper-left corner of the Advanced Monitoring tab, you can select the Shard, Mongos, or ConfigServer component type to view the monitoring data of a node corresponding to a role in a type of component.

   • If you set the Component Type parameter to ConfigServer, you can view the monitoring data of a node corresponding to the primary or secondary role in the ConfigServer component.

   • If you set the parameter to Shard, you can view the monitoring data of a node corresponding to the primary, secondary or readonly role in a shard component. The readonly role is displayed only when read-only nodes are added to the instance.

   Standalone instance

   You can view the monitoring data of the primary node in a standalone instance.

5. Change the time range during which you want to view monitoring data, the automatic update time of the monitoring data, and the time zone based on your business requirements. For more information, see Common time range controls.

   Note

   By default, monitoring data that is generated within the last 3 hours can be displayed.

6. View monitoring data. For more information about the metrics that can be viewed, see Monitoring items and metrics.

   • View the maximum, average, or current value of monitoring data within the current time range.

     In a metric trend chart, you can view the maximum, average, and current values of a metric within the current time range. max indicates the maximum value, avg indicates the average value, and current indicates the current value.

   • View monitoring data that is generated at a specific time point.

     Move the pointer over a time point in the x-axis of a trend chart of a metric to view the details of the metric at the time point.

   • View the monitoring data of a metric

     Move the pointer over the title of the metric whose monitoring data you want to view, click the icon next to the title, and then select an action. For more information, see Pods dashboard.