CloudMonitor displays the status and usage of ApsaraDB for Redis based on various metrics, including capacity usage and connection usage. Once you buy a Redis instance, CloudMonitor automatically starts monitoring the instance.

Once you buy a Redis instance, CloudMonitor automatically starts monitoring the instance. You can access the CloudMonitor page to view the metric data.  You can configure alarm rules for metrics so that an alarm is generated when any data exception occurs.

Monitoring service

  • Metrics
    Metric Definition Dimension Unit Minimum monitor Granularity
    Used capacity Redis capacity is currently in use Instance Bytes 1 minute
    Number of connections used Current total number of client connections Instance Number 1 minute
    Write speed Current write network traffic per second Instance BPS 1 minute
    Read Speed Network Traffic is currently read per second Instance BPS 1 minute
    Number of operation failures Number of times the current operation kvstore failed Instance Number 1 minute
    Percentage used capacity Proportion of current used capacity to total capacity Instance Percentage 1 minute
    Connection percentage used Current number of connections established as a percentage of total connections Instance Percentage 1 minute
    Write bandwidth usage Current write bandwidth as a percentage of total bandwidth Instance Percentage 1 minute
    Read bandwidth usage Current read bandwidth as a percentage of total bandwidth? Instance Percentage 1 minute
    Instance failure Event Type metrics, alarm rules can be set - - -
    Instance master standby switch Event Type metrics, alarm rules can be set - - -
  • Viewing Monitoring Data
    1. Log on to the CloudMonitor console.
    2. Go to the ApsaraDB for Redis instance list under Cloud Service Monitoring.  
    3. Click an instance name in the product instance list or click Monitoring Charts from the Actions column to access the instance monitoring details page.
    4. Click the Chart Size button to switch to large chart display (optional).

Alarm service

  • Parameter description
    • Metrics: The monitoring indicators provided by ECS for Redis.
    • Statistical cycle: The alarm rule system checks whether your monitoring data has exceeded the alarm rule 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.
    • Statistics: This sets the method used to determine if the data exceeds the threshold.   You can set Average, Maximum, Minimum, and Sum in Statistics.
      • 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.
    • Trigger an alarm after the threshold value has exceeded several times: This refers to the 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. The second time in 5 minutes to probe the CPU 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 alarm rules
    1. Log on to the CloudMonitor console.
    2. Go to the ApsaraDB for Redis instance list under Cloud Service Monitoring.  
    3. Click Alarm Rules in instance list Actions to access the instance’s Alarm Rules page.
    4. Enter all the relevant information in the required fields, and click Confirm to create a new alarm rule.