This topic describes how to configure alert rules for ApsaraDB for Redis in the CloudMonitor console. Alerts are immediately generated after the specified thresholds are exceeded or events are detected. This way, you can handle anomalies at the earliest opportunity.
CloudMonitor is a service that can be used to monitor Alibaba Cloud resources and Internet applications. The service is an all-in-one enterprise-class monitoring service that works out-of-the-box. You can create alert rules and specify the metrics based on which the 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.
The following table describes the alert types that are supported by CloudMonitor.
||Metrics vary based on instance types. Cluster instances and read/write splitting instances support metrics for data nodes and proxy nodes. For more information, see ApsaraDB for Redis of the standard edition, Redis Cluster, and Redis Read-Write.||When the value of a metric exceeds the specified threshold, for example, the CPU utilization
of an instance exceeds the 90% threshold, the system automatically sends an alert.
This helps you understand and handle anomalies at the earliest opportunity.
In most cases, workloads are sensitive to fluctuations in the CPU utilization, memory usage, and network traffic of the ApsaraDB for Redis instance. We recommend that you specify alert thresholds for the following key metrics:
|Create a threshold-triggered alert rule|
||If an ApsaraDB for Redis instance fails, performs a master-replica failover, or runs an automatic O&M task, the system automatically sends an alert. This allows you to resolve the issues at the earliest opportunity.||Subscribe to event notifications|