Setting Alarm Rules

Scenarios

You can set alarm rules to customize the monitored objects and notification policies and keep track of the instance status.

RDS alarm rules include alarm rule names, resource types, dimensions, monitored objects, metrics, alarm thresholds, monitoring period, and whether to send notifications.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. In the service list, choose Management & Deployment > Cloud Eye.
4. In the navigation pane, choose Alarm Management > Alarm Rules.
5. Click Create Alarm Rule in the upper right corner.
6. On the displayed page, set required parameters.
   • Basic information

     Table 1 Basic information

     Parameter	Description
     Name	Alarm rule name. The system generates a random name, which you can modify. Example value: alarm-wnat
     Description	Description of the alarm rule.

   • Alarm parameters

     Table 2 Alarm parameters

     Parameter	Description
     Alarm Type	Select Metric.
     Cloud Product	Select Relational Database Service - MariaDB Instances.
     Resource Level	Cloud product is recommended.
     Monitoring Scope	All resources: An alarm will be triggered if any resource of the current cloud product meets the alarm policy. To exclude resources that do not require monitoring, click Select Resources to Exclude. Specific resources: Click Select Specific Resources to select resources.
     Method	Associate template: After an associated template is modified, the policies contained in this alarm rule to be created will be modified accordingly. You are advised to use an existing template. The existing template already contains three common alarm metrics: CPU usage, memory usage, and storage space usage. Configure manually: Configure alarm policies as needed.
     Template	If you select Associate template for Method, select a template. You can select a default alarm template or create a custom template.
     Alarm Policy	If you select Configure manually for Method, you need to configure alarm policies. An alarm is triggered when the metric configured for this alarm reaches the preset threshold in consecutive periods. For example, Cloud Eye triggers an alarm every 5 minutes if the average CPU usage of the monitored object is 80% or more for three consecutive 5-minute periods. NOTE: A maximum of 50 alarm policies can be added to an alarm rule. If any of these alarm policies are met, an alarm will be triggered.
     Alarm Severity	The alarm severity can be Critical, Major, Minor, or Warning.

   • Alarm notification parameters

     Table 3 Alarm notification parameters

     Parameter	Description
     Alarm Notification	Whether to notify users when alarms are triggered. Notifications can be sent by email, text message, or HTTP/HTTPS message.
     Notification Object	Object the alarm notification is to be sent to. You can select the account contact or a topic. The account contact is the mobile phone number and email address of the registered account. A topic is a specific event type for publishing messages or subscribing to notifications.
     Notification Window	Cloud Eye sends notifications only within the notification window specified in the alarm rule. If Notification Window is set to 08:00-20:00, Cloud Eye sends notifications only within 08:00-20:00.
     Trigger Condition	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.

7. After the configuration is complete, click Create.