Setting Alarm Rules
Scenarios
You can set alarm rules to customize the monitored objects and notification policies and keep track of the RDS running status.
RDS alarm rules include alarm rule names, resource types, dimensions, monitored objects, metrics, alarm thresholds, monitoring period, and whether to send notifications.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Management & Governance, click Cloud Eye.
- In the navigation pane on the left, choose Cloud Service Monitoring > Relational Database Service.
Figure 1 Choosing a monitored object
- Locate the instance you want to add an alarm rule for and click Create Alarm Rule in the Operation column.
- 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
(Optional) Supplementary information about the alarm rule.
- Alarm parameters
Figure 2 Alarm parameters
Table 2 Alarm parameters Parameter
Description
Method
You are advised to select Use existing template. The existing templates already contain three common alarm metrics: CPU usage, memory usage, and storage space usage.
NOTE:If you select Associate template, after the associated template is modified, the policies contained in this alarm rule to be created will be modified accordingly.
Template
Select the template to be used.
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 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 one of these alarm policies is met, an alarm is triggered.
Alarm Severity
If you select Configure manually for Method, you need to configure alarm severity. The alarm severity can be Critical, Major, Minor, or Informational.
- Alarm notification parameters
Figure 3 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 Recipient
You can select a notification group or topic subscription as required.
Notification Group
Notification group the alarm notification is to be sent to.
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 used to publish messages and 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 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.
- Advanced settings
Table 4 Advanced settings Parameter
Description
Enterprise Project
Enterprise project that the alarm rule belongs to. Only users with the enterprise project permissions can view and manage the alarm rule.
Tag
A tag is a key-value pair. Tags identify cloud resources so that you can easily categorize and search for your resources.
- A key can contain a maximum of 128 characters, and a value can contain a maximum of 225 characters.
- A maximum of 20 tags can be added.
- Basic information
- After the configuration is complete, click Create.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot