Global Distributed Cache for Redis has been connected to CloudMonitor. You can configure an alert rule in the CloudMonitor console to monitor the synchronization latency of child instances. This way, you can be notified of synchronization exceptions immediately when they occur, and take measures at the earliest opportunity.
CloudMonitor introduction
CloudMonitor is a service that monitors Alibaba Cloud resources and Internet applications. CloudMonitor helps you improve system service availability and reduce the O&M costs of IT infrastructure.
Procedure
- Log on to the CloudMonitor console.
- In the left-side navigation pane, choose .
- On the Alert Rules page, click Create Alert Rule.
- In the Create Alert Rule panel, configure the parameters. The following table describes the parameters.
Parameter Description Product The product for which you create the alert rule. Select Tair DRAM-based Instances (Standard Architecture), Tair DRAM-based Instances (Cluster Architecture), or Tair DRAM-based Instances (Read/Write Splitting Architecture). Note You can enter Redis in the search box to quickly find the Tair service.Resource Range The range of the resources to which the alert rule applies. Valid values: - All Resources: The alert rule applies to all resources of the specified cloud service.
- Application Group: The alert rule applies to all resources in the specified application group of the specified cloud service.
- Instances: The alert rule applies to the specified resources of the specified cloud service.
Rule Description The description of the alert rule. If a metric meets the specified condition, an alert is triggered. To specify the rule description, perform the following steps: - Click Add Rule.
- In the Add Rule Description panel, specify the rule name, metric type, metric, threshold, and alert level.
In this example, the metric of the alert rule is set to
. If the average value within 5 minutes is greater than 60 seconds, the alert is triggered. - Click OK.
Note For information about how to specify complex alert conditions, see Alert rule expressions.Mute for The interval at which you want CloudMonitor to resend alert notifications when the alert is not cleared. Valid values: 5 Minutes, 15 Minutes, 30 Minutes, 60 Minutes, 3 Hours, 6 Hours, 12 Hours, and 24 Hours. If the threshold value is exceeded, CloudMonitor sends an alert notification. If the threshold value is exceeded again within the mute period, CloudMonitor does not resend an alert notification. If the alert is not cleared after the mute period ends, CloudMonitor resends an alert notification.
For example, if the Mute For parameter is set to 12 Hours and the alert is not cleared, Cloud Monitor resends an alert notification after 12 hours.
Effective Period The period of time during which you want the alert rule to take effect. CloudMonitor monitors the specified resources based on the alert rule only within the specified period of time. Alert Contact Group The alert contact group to which alert notifications are sent. The alert notifications of the application group are sent to the alert contacts that belong to the selected alert contact group. An alert contact group can contain one or more alert contacts.
For information about how to create an alert contact and an alert contact group, see Create an alert contact or alert contact group.
Alert Callback The URL that is used to receive the alert notifications sent from CloudMonitor by using HTTP POST requests. The URL must be accessible over the Internet. You can enter only an HTTP URL. For information about how to configure alert callbacks, see Use the alert callback feature to send notifications about threshold-triggered alerts.
To test the connectivity of an alert callback URL, perform the following steps:- Click Test next to the the callback URL. In the WebHook test panel, you can check and troubleshoot the connectivity of the alert callback URL based on the returned status code and test result details.Note To obtain the details of the test result, configure the Template Type and Language parameters and click Test.
- Click Close.
Auto Scaling (The corresponding scaling rule will be triggered when the alert occurs.) If you turn on Auto Scaling (The corresponding scaling rule will be triggered when the alert occurs.) and an alert is triggered, the specified scaling rule is enabled. In this case, you must configure the Region, ESS Group, and ESS Rule parameters. - For information about how to create a scaling group, see Manage scaling groups.
- For information about how to create a scaling rule, see Manage scaling rules.
Log Service (If you select Log Service, the alert information will be written to Log Service.) If you turn on Log Service (If you select Log Service, the alert information will be written to Log Service.) and an alert is triggered, the alert information is written to the specified Logstore in Log Service. In this case, you must configure the Region, ProjectName, and Logstore parameters. For information about how to create a project and a Logstore, see Getting Started.
Message Service - Topic If you turn on Message Service - Topic and an alert is triggered, the alert information is written to the specified topic in Message Service (MNS). In this case, you must configure the Region and topicName parameters. For information about how to create a topic, see Create a topic.
Method to handle alerts when no monitoring data is found The method that you want to use to handle alerts when no monitoring data is found. Valid values: - Do not do anything (default value)
- Send alert notifications
- Treated as normal
Note To configure Alert Callback, Auto Scaling (The corresponding scaling rule will be triggered when the alert occurs.), Log Service (If you select Log Service, the alert information will be written to Log Service.), Message Service - Topic, and Method to handle alerts when no monitoring data is found, click Advanced Settings. - Click OK.