Configuring an Alarm Rule

Scenarios

Setting alarm rules allows you to customize objects to be monitored and notification policies so that you can closely monitor your instances.

Alarm rules include the alarm rule name, instance, metric, threshold, monitoring interval, and whether to send notifications. This section describes how to set alarm rules.

Usage Notes

A maximum of 50 alarm policies can be added to an alarm rule. If any policy is met, an alarm will be triggered.

Procedure

1. Log in to the Cloud Eye console.
2. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
3. On the Alarm Rules page, click Create Alarm Rule.
4. Set alarm parameters.
   Figure 1 Configuring an alarm rule
   

   Table 1 Alarm rule parameters

   Parameter	Description
   Parameter	Alarm rule name. The system generates a random name, and you can change it if needed.
   Description	Alarm rule description. This parameter is optional.
   Alarm Type	Alarm type to which the alarm rule applies. You can select Metric or Event.
   Cloud Product	Select GeminiDB - Redis instance.
   Resource Level	Cloud product is recommended.
   Monitoring Scope	Monitoring scope the alarm rule applies to. You can select All resources, Resource groups, or Specific resources. NOTE: All resources: An alarm will be triggered if any resource of the selected cloud product meets the alarm policy. Resource groups: An alarm will be triggered if any resource in the selected resource group meets the alarm policy. Specific resources: Click Select Specific Resources to select resources. An alarm will be triggered if any selected resource meets the alarm policy.
   Method	Method for configuring an alarm policy. You can select Associate template or Configure manually. Associate template: If you need to configure the same alarm rule for multiple groups of resources under the same cloud product, you can use an alarm template to simplify operations. You are advised to select an existing template. The existing templates already contain three common alarm metrics: CPU usage, memory usage, and storage space usage. Configure manually: You can create custom alarm policies as needed.
   Template	If you select Associate template for Method, you need to select a template. You can select a default alarm template or create a custom template.
   Alarm Policy	Policy for triggering an alarm. You can adjust the threshold, consecutive periods, alarm interval, and alarm severity. Metric Name: metric for which the alarm rule is created The following metrics are recommended: Storage Space Usage (instance-level): It indicates the storage usage of GeminiDB Redis instances. If the storage usage is greater than 80%, scale up the storage in a timely manner. CPU Usage and Memory Usage (node-level): It indicates the compute usage of each node in a GeminiDB Redis instance. If the CPU usage or memory usage is greater than 80%, you can add nodes or upgrade node specifications in a timely manner. For more metrics, see Supported Metrics. Alarm Severity: the severity of an alarm, which can be Critical, Major, Minor, or Warning. NOTE: A maximum of 50 alarm policies can be added to an alarm rule. If any of the policies is met, an alarm is triggered.

   Figure 2 Configuring alarm notifications
   

   Table 2

   Parameter	Description
   Alarm Notifications	Controls whether users are notified when alarms are triggered. Notifications can be sent by email, text message, or HTTP/HTTPS requests. Enabling this function is recommended. When a metric reaches the threshold set in the alarm rule, Cloud Eye immediately informs you of the exception through text messages.
   Notified By	Notification method. You can select Notification policies, Notification groups, or Topic subscriptions.
   Notification Policies	Select one or more notification policies if you select Notification policies for Notified By. You can specify the notification groups, window, template, and other parameters in a notification policy. For details about how to create a notification policy, see Creating, Modifying, or Deleting a Notification Policy.
   Notification Group	Notification group that needs to send alarm notifications.
   Recipient	Object the alarm notification is to be sent to. You can select the account contact or a topic. Account contact indicates a mobile number and an email address registered during account creation A topic is used to publish messages or subscribe to notifications. If the required topic is unavailable, create one first and add subscriptions to it. For details, see Creating a Topic and Adding Subscriptions.
   Notification Template	This parameter is only available if you select Notification groups or Topic subscriptions for Notified By. You can select an existing template or create a new one to send alarm notifications.
   Validity Period	Time window during which Cloud Eye sends notifications. If you set Notification Window to 08:00-20:00, Cloud Eye sends notifications only within this period.
   Trigger Condition	The condition for triggering an alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.

   Figure 3 Advanced Settings
   

   Table 3

   Parameter	Description
   Enterprise Project	Enterprise project that the alarm rule belongs to. Only users who have the permissions for the enterprise project can manage this alarm rule. For details, see Creating an Enterprise Project.
   Tag	Tags are key–value pairs. You can tag cloud resources to easily categorize and search for them. You are advised to create predefined tags in Tag Management Service (TMS). For details, see Creating Predefined Tags. A key can contain up to 128 characters, and a value can contain up to 255 characters. You can add up to 20 tags.

5. After the configuration is complete, click Create.

   When the metric data reaches the threshold set in the alarm rule, Cloud Eye immediately notifies you through SMN that an exception has occurred.

   

   For more information about alarm rules, see Cloud Eye User Guide.