Configure an alert rule in CloudMonitor to track the synchronization latency between child instances of a Tair (Redis OSS-compatible) Global Distributed Cache distributed instance. When latency exceeds a threshold, CloudMonitor sends an alert notification automatically so you can detect and respond to data consistency issues before they affect your application.
Cloud Monitor is a service that monitors Alibaba Cloud resources and internet applications. It helps you improve the uptime of your services and reduce IT operations and maintenance (O&M) costs.
Prerequisites
Before you begin, make sure that you have:
-
A Tair (Redis OSS-compatible) Global Distributed Cache distributed instance
-
An alert contact group configured in CloudMonitor. For instructions, see Create an alert contact or alert contact group
Create an alert rule for synchronization latency
-
Log on to the Cloud Monitor console.
-
In the left-side navigation pane, choose Alerts > Alert Rules.
-
On the Alert Rules page, click Create Alert Rule.
-
On the Create Alert Rule page, configure the following parameters:
Parameter Description Product Select the product that matches the architecture of your distributed instance: Redis/Tair DRAM (Standard), Redis/Tair DRAM (Cluster), or Redis/Tair DRAM (Read/Write Splitting). Enter Redisin the search box to filter options.Resource Range The resources to which the alert rule applies. Options: All Resources (all resources of the selected product), Application Groups (all resources in a specific application group), or Instances (specific instances). Rule Description The alert condition. Click Add Rule, then configure the following in the Configure Rule Description panel: the rule name, metric type, metric (multi active sync delay time), threshold, alert level, and alert method. Click OK when done. For example, set the rule to trigger when the average value of multi active sync delay time over a 5-minute period exceeds 60 seconds. For complex alert conditions, see Alert rule expressions. Mute For How long CloudMonitor waits before resending an alert if the condition is not cleared. Options: 5 minutes, 15 minutes, 30 minutes, 60 minutes, 3 hours, 6 hours, 12 hours, or 24 hours. CloudMonitor sends an alert notification when a metric value reaches the threshold. If the metric value reaches the threshold again within the mute period, CloudMonitor does not resend an alert notification. After the mute period ends, CloudMonitor resends the alert if the condition persists. Effective Period The time window during which the alert rule is active. CloudMonitor only evaluates alert conditions within this period. Alert Contact Group The contact group that receives alert notifications. A contact group can include one or more alert contacts. For other parameters, keep the default values. For details, see Create an alert rule.
-
Click Confirm.