This topic describes how to configure alert rules for ApsaraDB for Redis in the CloudMonitor console. Alarms are immediately generated after the specified thresholds are exceeded or events are detected. This way, you can handle exceptions at the earliest opportunity.

Background information

CloudMonitor is a service that can be used to monitor Alibaba Cloud resources and Internet applications. The service is an all-in-one enterprise-grade monitoring service that works out-of-the-box. For more information, see What is CloudMonitor? You can create alert rules and specify the metrics based on which alerts are triggered. When the alert rules of a specified metric are triggered, alerts are generated and sent to alert contacts in an alert contact group.

Note CloudMonitor sends alerts to alert contacts in alert contact groups. Before you add an alert contact to an alert contact group, you must create the alert contact or alert contact group. For more information, see Create an alert contact or alert group.


  1. Log on to the ApsaraDB for Redis console.
  2. In the top navigation bar of the page, select the region in which the instance you want to monitor is deployed.
  3. On the Instances page, click the ID of the instance.
  4. In the left-side navigation pane, click Alarm Settings.
  5. On the Alarm Settings page, view monitoring metrics of the current instance. You can also click Alert Settings in the upper-right corner to go to the CloudMonitor console to add or manage alert rules. Alarm Settings page

    The following table describes the alert types that are supported by CloudMonitor.

    Alert type Instance architecture Metric Description References
    Threshold-triggered alerts

    When you create a threshold-triggered alert rule, you must specify the architecture of the instance to be associated with the alert. The following instance architectures are supported:

    Select associated instance architectures
    • ApsaraDB for Redis standard instances
    • ApsaraDB for Redis cluster instances
    • ApsaraDB for Redis read/write splitting instances
    • ApsaraDB for Redis Enhanced Edition (Tair) storage-optimized master-replica instances
    • ApsaraDB for Redis Enhanced Edition (Tair) persistent memory-optimized standard instances
    • ApsaraDB for Redis Enhanced Edition (Tair) persistent memory-optimized cluster instances
    Metrics vary based on instance architectures. Cluster instances support metrics for data nodes, and read/write splitting instances support metrics for proxy nodes. For more information, see Redis Standard, Redis Cluster, and Redis Read-Write. When the value of a metric exceeds the specified threshold, the system automatically sends an alert. For example, if the CPU utilization of an ApsaraDB for Redis instance exceeds the 90% threshold, the system sends an alert. This enables you to understand and respond to exceptions in a timely manner.

    In most cases, workloads are sensitive to fluctuations in the CPU utilization, memory usage, and network traffic of an ApsaraDB for Redis instance. We recommend that you specify alert thresholds for the key metrics. The following metrics and thresholds are provided for your reference:

    • CPU utilization: greater than 60%.
    • Memory usage: greater than 80%.
    • Inbound bandwidth usage and outbound bandwidth usage: greater than 80%.
    • Disk usage: greater than 80%. This threshold applies only to ApsaraDB for Redis Enhanced Edition (Tair) storage-optimized master-replica instances.
    Create a threshold-triggered alert rule
    Event-triggered alerts N/A
    • InstanceMaintenance (proactive O&M events)
    • Exceptions
    • Maintenance
    If an ApsaraDB for Redis instance fails, triggers a master-replica switchover, or runs a proactive O&M task such as an instance migration, the system automatically sends an alert. This allows you to resolve the issues in a timely manner. Subscribe to event notifications