RDS monitoring

Last Updated: Sep 28, 2017

CloudMonitor displays the ApsaraDB for RDS operation status based on four metrics: Disk usage, IOPS usage, Connection usage, and CPU usage. Once you buy ApsaraDB for RDS products, CloudMonitor will automatically start monitoring the above four metrics without any additional operations.

Note

  • RDS only provides monitoring and alarm services for primary and read-only instances.

  • By default, CloudMonitor will create alarm rules for each primary instance and read-only instance. These rules set up the thresholds of CPU usage, Connection usage, IOPS usage, and Disk usage all to 80%. When metric data exceeds any of the above thresholds, a text message and an email will be sent to the alarm contact account.

Monitoring service

Metric description

Metric Definition Dimension Units Minimum monitoring granularity
Disk usage The percentage of disk space used by the RDS instance. Instance Percentage 5 minutes
IOPS usage The percentage of IO requests per second used by the RDS instance. Instance Percentage 5 minutes
Connection usage The connection count is the number of connections that application programs can establish with the RDS instance. Connection usage is the percentage of these connections currently in use. Instance Percentage 5 minutes
CPU usage The percentage of CPU capacity consumed by the RDS instance (CPU performance is determined by the database memory size.). Instance Percentage 5 minutes
Memory usage The percentage of the RDS instance’s memory in use. Currently, the memory usage metric is only supported by MySQL databases. Instance Percentage 5 minutes
Incoming network traffic The instance’s input traffic per second. Instance bit/s 5 minutes
Outgoing network traffic The instance’s output traffic per second. Instance bit/s 5 minutes

Note: The incoming and outgoing network traffic metrics are only supported by MySQL and SQLServer databases.

View metric data

  1. Log on to the CloudMonitor console.

  2. Go to the RDS instance list under Cloud Service Monitoring.

  3. Click an instance name in the product instance list or click Monitoring Charts in the Actions column to access the instance monitoring details page.

  4. (Optional) Click the Chart Size button to switch to large chart display mode.

Alarm rules

Parameter description

  • Metric: It is the monitoring indicator provided by RDS.

  • 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.

  • Statistic: This sets the method used to determine if the data exceeds the threshold. You can set Average, Maximum, Minimum, and Sum in Statistic.

    • 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 the statistical cycle. When the sum of the metric data collected within the statistical cycle is over 80%, it exceeds the threshold. The above statistics are needed for traffic-based indicators.

  • Trigger an alarm after the threshold value has exceeded several times: This refers to an alarm which is triggered when the value of the metric 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 Statistical cycle (the quantity of consecutive detection times - 1) = 5*(3-1) = 10 minutes.

Set an alarm rule

  1. Log on to the CloudMonitor console.

  2. Go to the ApsaraDB for RDS instance list under Cloud Service Monitoring.

  3. Click Alarm Rules from the Actions columns to access the instance’s alarm rules page.

  4. Enter relevant information in the required fields and click Confirm to create a new alarm rule.

Thank you! We've received your feedback.