Cloud monitoring through monitoring multiple monitors such as CPU usage, memory usage, and so on for MongoDB service instances of cloud Database item, helps the user monitor the running status of the instance and supports the user to set alarm rules on the monitoring item. User purchases After the MongoDB service, cloud monitoring automatically collects data for the above monitoring items.

Monitoring Services

  • Monitoring items
    Monitoring items Meaning Dimensions Unit Minimum monitor Granularity
    CPU utilization CPU usage for instance User dimension, instance dimension, Master dimension Percentage 5 minutes
    Memory usage Memory usage for instance User dimension, instance dimension, Master dimension Percentage 5 minutes
    Disk usage Disk usage for an instance User dimension, instance dimension, Master dimension Percentage 5 minutes
    IOPS usage Iops usage for instances User dimension, instance dimension, Master dimension Percentage 5 minutes
    Connections usage The number of connections is the number of instances that an application can connect to a MongoDB. Number of connections usage is the percentage of the number of connections that have been used User dimension, instance dimension, Master dimension Percentage 5 minutes
    Average number of SQL queries per second Average number of SQL queries per second for MongoDB instances User dimension, instance dimension, Master dimension Number 5 minutes
    Number of connections usage The number of instances of MongoDB that the current application connects User dimension, instance dimension, Master dimension Number 5 minutes
    The amount of disk space used by the instance Total amount of disk space actually used by the instance User dimension, instance dimension, Master dimension Bytes 5 minutes
    Amount of disk space occupied by data The amount of disk space used by the data User dimension, instance dimension, Master dimension Bytes 5 minutes
    Log usage of disk space The amount of disk space occupied by the log User dimension, instance dimension, Master dimension Bytes 5 minutes
    Inbound Intranet traffic Network Flow Traffic for an instance User dimension, instance dimension, Master dimension Bytes 5 minutes
    Outbound Intranet traffic Network Flow Traffic for an instance User dimension, instance dimension, Master dimension Bytes 5 minutes
    Request count Total number of requests sent to the server User dimension, instance dimension, Master dimension Number 5 minutes
    Number of insert operations The number of times the INSERT command was last started from the MongoDB instance to the current cumulative receipt User dimension, instance dimension, Master dimension Number 5 minutes
    Number of query operations The number of times the query command was recently started from the MongoDB instance to the query command that is now cumulative User dimension, instance dimension, Master dimension Bytes 5 minutes
    Number of update operations The number of times the update command was recently started from the MongoDB instance to the update command that is now cumulative User dimension, instance dimension, Master dimension Number 5 minutes
    Number of delete operations The number of operations from the last time the MongoDB instance was started to now cumulative execution of Delete User dimension, instance dimension, Master dimension Number 5 minutes
    Number of operations from getmore The number of operations from the last time the MongoDB instance was started to the present cumulative execution of getmore User dimension, instance dimension, Master dimension Number 5 minutes
    Command operation count The total number of commands sent to the database since the last time MongoDB was started. User, instance, and master/backup Number 5 minutes
    Instance failure Event-type metric, for which alarm rules can be set - - -
    Note
    • Metric data can be saved for up to 31 days.

    • You can view metric data for up to 14 consecutive days.

  • View metric data
    1. Log on to CloudMonitor console.
    2. Go to the ApsaraDB for MongoDB instance list under Cloud Service Monitoring.
    3. Click an instance name in the product instance list or click Metric Chart from the Actions column to view metrics on the Instance monitoring details page.
    4. Click the Time Range shortcut at the top of the page or use the specific selection function. Data for up to 14 consecutive days can be viewed.
    5. Click the Zoom In button in the upper-right corner of the metric chart to enlarge the graph.

Alarm service

  • Parameter descriptions
    • Metric items: The monitoring indicators provided by ApsaraDB for MongoDB.
    • Statistical cycle: The alarm system checks whether your monitoring data has exceeded the alarm threshold value based on the statistical cycle. For example, if the statistical cycle of the alarm rule for memory usage is set to one minute, the system checks whether the memory usage has exceeded the threshold value every other minute.
    • Statistical method: This sets the method used to determine if the data exceeds the threshold. You can set Average, Maximum, Minimum, and Sum in Statistical method.
      • Average: The average value of metric data within a statistical cycle. The statistical result is the average of all metric data collected within 15 minutes. An average value of over 80% is deemed to exceed the threshold.
      • Maximum: The maximum value of metric data within a statistical cycle. When the maximum value of the metric data collected within the statistical cycle is over 80%, the value exceeds the threshold.
      • Minimum: The minimum value of metric data within a statistical cycle. When the minimum value of the metric data collected within the statistical cycle is larger than 80%, the value exceeds the threshold.
      • Sum: The sum of metric data within a statistical cycle. When the sum of the metric data collected within the statistical cycle is over 80%, it exceeds the threshold. The preceding statistical methods are required for traffic-based indicators.
    • Consecutive times: Refers to an alarm which is triggered when the value of the metric item continuously exceeds the threshold value in several consecutive statistical cycles.

      For example, you may set the alarm to go off when the CPU usage rate exceeds 80% within a 5-minute statistical cycle after the threshold value is exceeded for three times. If the CPU usage rate is found to exceed 80% for the first time, no warning notification is sent. No alarm is reported if the CPU usage rate exceeds 80% only twice in a row. An alarm is reported only if the CPU usage rate exceeds 80% for the third time. That is, from the first time when the actual data exceeds the threshold to the time when the alarm rule is triggered, the minimum time consumed is the statistical cycle*(the quantity of consecutive detection times-1) = 5*(3-1) = 10 minutes.

  • Set a single alarm rule
    1. Log on to CloudMonitor console.
    2. Choose Cloud Service Monitoring > ApsaraDB for MongoDB .
    3. Click the Instance name or the monitor chart in the operation to enter the monitoring details page for the instance.
    4. Click the bell button in the upper-right corner of the monitor chart to set alarm rules for the monitoring items corresponding to the instance.
  • Set up bulk alarm rules
    1. Log in to the cloud monitoring console.
    2. Go to MongoDB, a cloud Database monitored by cloud services List of version instances.
    3. When the instance list page selects the desired instance, click set alarm rule below the page, you can add alarm rules in bulk.