By monitoring multiple metrics from ApsaraDB for MongoDB, such as CPU usage and memory usage, CloudMonitor helps you to monitor the running status of instances. CloudMonitor automatically begins to collect data for the metrics after you purchase the MongoDB service.

Monitoring service

  • Metrics
    Metric Description Dimension Unit Minimum monitoring granularity
    CPU Usage The percentage of CPU in use of the instance User, instance, and master/salve % 5 minutes
    Memory Usage The memory in use of the instance User, instance, and master/slave % 5 minutes
    Disk Usage The disk space in use of the instance User, instance, and master/slave % 5 minutes
    IOPS Usage The percentage of the actual IOPS to the maximum IOPS of the instance User, instance, and master/slave % 5 minutes
    Connection Usage The number of connections is the number of instances that an application can connect to a MongoDB instance. Connection usage is the percentage of the connections currently in use. User, instance, and master/slave % 5 minutes
    Number of Query Operations The number of SQL queries per second of the instance User, instance, and master/slave Count 5 minutes
    Connection Usage The number of connections in use User, instance, and master/slave Count 5 minutes
    Disk Size Occupied by Instances Total amount of disk space in use of the instance User, instance, and master/slave Byte 5 minutes
    Disk Size Occupied by data The amount of disk space used by data User, instance, and master/slave Byte 5 minutes
    Disk Size Occupied by logs The amount of disk space used by logs User, instance, and master/slave Byte 5 minutes
    Intranet Inbound Traffic The network inbound traffic for an instance User, instance, and master/slave Byte 5 minutes
    Intranet Outbound Traffic The network outbound traffic for an instance User, instance, and master/slave Byte 5 minutes
    Number of Requests Total number of requests sent to the server User, instance, and master/slave Count 5 minutes
    Number of Insert Operations The number of Insert commands received during the time from the last start of the instance to the current time User, instance, and master/slave Count 5 minutes
    Number of Query Operations The number of Query commands received during the time from the last start of the instance to the current time User, instance, and master/slave Byte 5 minutes
    Number of Update Operations The number of Update commands received during the time from the last start of the instance to the current time User, instance, and master/slave Count 5 minutes
    Number of Delete Operations The number of Delete commands executed during the time from the last start of the instance to the current time User, instance, and master/slave Count 5 minutes
    Number of Getmore Operations The number of Getmore commands executed during the time from the last start of the instance to the current time User, instance, master/slave Count 5 minutes
    Number of Command Operations The total number of commands sent to the database during the time from the last start of the instance to the current time User, instance, and master/slave Count 5 minutes
    Instance Failure Event-type metric, for which alarm rules can be set N/A N/A N/A
    Note
    • Monitoring data is saved for up to 31 days.
    • You can view metric data for up to 14 consecutive days at a time.
  • View monitoring data
    1. Log on to the CloudMonitor console.
    2. In the left-side navigation pane, choose Cloud Service Monitoring > ApsaraDB for MongoDB.
    3. Select the region to which the target instance belongs and select the instance type.
    4. Find the target instance and click the instance name or click Monitoring Charts from the Actions column.
    5. Select the Time Range by clicking the time duration button or choose a custom time range. You can view the monitoring data in up to 14 days at a time.
    6. To switch to a larger view, click the enlargement icon in the upper-right corner of the chart.

Alarm service

  • Set a single alarm rule
    1. Log on to the CloudMonitor console.
    2. In the left-side navigation pane, choose Cloud Service Monitoring > ApsaraDB for MongoDB.
    3. Select the region to which the target instance belongs and select the instance type.
    4. Find the target instance and click the instance name or click Monitoring Charts from the Actions column.
    5. On the Monitoring Charts tab page, click the bell icon in the upper-right corner of a chart to set an alarm rule.
  • Set alarm rules in batches
    1. Log on to the CloudMonitor console.
    2. In the left-side navigation pane, choose Cloud Service Monitoring > ApsaraDB for MongoDB.
    3. Select the target instances on the instance list page. Then, click Set Alarm Rules below the list to add alarm rules in batches.
  • Parameters
    • Products: ECS, RDS, OSS, among others
    • Resource Range: the range for which an alarm rule takes effect. There are two alarm rule ranges available: All Resources and Instances.
      • All Resources: Indicates that the specified alarm rule applies to all MongoDB instances under your account. For example, if you set the resource range to All Resources, and set the alarm threshold for CPU usage to 80%, then an alarm is triggered when the CPU usage of any MongoDB instance exceeds 80%. When you select All Resources, you can report alarms for up to 1,000 resources. If the number of your resources exceeds 1,000, alarms cannot be reported for some resources even if they exceed the threshold you set in your alarm rule. Therefore, for these scenarios, we recommend that you use application groups to divide resources by service before setting up alarm rules to avoid this issue.
      • Instances: Indicates that the specified rule only applies to a specific instance. For example, if you set the resource range to Instances and set the alarm threshold for inbound traffic to 100 MB, an alarm is triggered when the inbound traffic of the specified instance exceeds 100 MB.
    • Alarm Rule: the alarm rule name
    • Rule Describe: the main content of the alarm rule where you define the alarm-triggering conditions, or value threshold, for related metrics. For example, if you describe the rule as 5mins Average Inbound Traffic >= 100 MB, the alarm service will check every five minutes whether the average value of inbound traffic within five minutes meets or exceeds 100 MB.

      Consider the following example. For the alarm service in host monitoring, one data point is reported in 15 seconds for a single server metric, and 20 data points in five minutes. This relates to the following alarm rules.

      • 5mins Average CPU Usage > 90%: The average CPU usage value of the 20 data points in five minutes exceeds 90%.
      • 5mins CPU Usage Always > 90%: The CPU usage values of the 20 data points in five minutes all exceed 90%.
      • 5mins CPU Usage Once > 90%: The CPU usage value of at least one of the 20 data points in five minutes exceeds 90%.
      • Total 5mins Internet Outbound Traffic > 50 MB: The sum of the outbound traffic values of the 20 data points in five minutes exceeds 50 MB.
    • Mute For: the period of time that an alarm has been muted so that alarm contacts do not receive any alarm notifications during this period. An alarm rule can be muted up to 24 hours (or 1 day).
    • Triggered when threshold is exceeded for: An alarm notification is sent if the detected values reach the alarm rule threshold a certain number of times consecutively. For example, if you set this parameter to 3 and set Rule Describe to 5mins Average CPU Usage > 80%, only when the average CPU usage in five minutes is detected to be greater than 80% for three times in a row, will an alarm be triggered.
    • Effective Period: the period of time for which an alarm rule is effective. During this period of time, the alarm service checks metric data and determines whether to generate an alarm.
    • Notification Contact: a group of contacts who receive alarm notifications.
    • Notification Methods: Email and DingTalk chatbot.
    • Email Subject: The email subject is set as the product name, metric, and instance ID involved in the alarm by default.
    • Email Remark: supplementary information customized for an alarm email. Remarks are sent as part of the alarm notification email.
    • HTTP CallBack: Enter a URL accessible through the Internet and CloudMonitor will push the alarm information to the address through a POST request. Currently, only HTTP is supported.