Creating an Alarm Rule
Scenarios
The alarm function provides the alarm service for monitoring data. By creating alarm rules, you define how the alarm system checks monitoring data and sends alarm notifications when metric data meets alarm policies.
After creating alarm rules for important metrics, you can timely know metric data exceptions and quickly rectify the faults.
Functions
- Alarm rules can be created for all monitoring items on Cloud Eye.
- Alarm rules can be created for all resources, resource groups, log monitoring, custom monitoring, event monitoring, and website monitoring.
- You can set validity periods of alarm rules, that is, customize the time when alarm rules take effect.
- Notifications can be sent by email, text message, or HTTP/HTTPS message.
Procedure
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Alarm Management > Alarm Rules, and click Create Alarm Rule in the upper right corner.
- On the Create Alarm Rule page, configure the parameters.
- Set the alarm rule name and description.
Table 1 Name and Description Parameter
Description
Name
Specifies the alarm rule name. The system generates a random name, which you can modify.
Example value: alarm-b6al
Description
(Optional) Provides supplementary information about the alarm rule.
- Select a monitored object and configure alarm content parameters.
Table 2 Alarm Content parameters Parameter
Description
Example Value
Alarm Type
Specifies the alarm type to which the alarm rule applies. The value can be Metric or Event.
Metric
Resource Type
Specifies the type of the resource the alarm rule is created for.
Elastic Cloud Server (ECS)
Dimension
Specifies the metric dimension of the selected resource type.
ECSs
Monitoring Scope
The monitoring scope of an alarm rule can be All resources, Resource groups, or Specified resources.
NOTE:- If you select All resources, an alarm notification will be sent when any instance meets an alarm policy, and existing alarm rules will be automatically applied for newly purchased resources.
- If Resource groups is selected and any resource in the group meets the alarm policy, an alarm is triggered.
- If you select Specific resources, select one or more resources and click to add them to the box on the right.
All resources
Method
There are three options: Associate template, Use existing template, and Configure manually.
NOTE:After an associated template is modified, the policies contained in this alarm rule to be created will be modified accordingly.
Create manually
Template
Specifies the template to be used.
You can select a default alarm template or customize a template.
N/A
Alarm Policy
Specifies the policy for triggering an alarm.
If you set Resource Type to Custom Monitoring, or a specific cloud service, whether to trigger an alarm depends on whether the metric data in consecutive periods reaches the threshold. 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.
If you set Resource Type is to Event Monitoring, the event that triggers the alarm is an instant event. For example, if event improper ECS running occurs, Cloud Eye triggers an alarm.
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.
N/A
Alarm Severity
Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.
Major
- Configure the alarm notification.
Figure 1 Alarm Notification parameters
Table 3 Alarm Notification parameters Parameter
Description
Alarm Notification
Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, text message, or HTTP/HTTPS message.
Notification Object
Specifies the object to which alarm notifications will be sent. You can select the account contact or a topic.
- Account contact is the mobile 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.
Validity Period
Cloud Eye sends notifications only within the notification window you specified.
If Validity Period is set to 08:00-20:00, Cloud Eye sends notifications only within 08:00-20:00.
Trigger Condition
Specifies the condition for triggering the alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.
- Configure the Enterprise Project and Tag.
Figure 2 Advanced Settings
Table 4 Name and Description Parameter
Description
Enterprise Project
Specifies the enterprise project that the alarm rule belongs to. Only users who have all permissions for the enterprise project can view and manage the alarm rule. For details about how to create an enterprise project, see Creating an Enterprise Project.
Tag
A tag consists of a key-value pair. Tags can be used to categorize and search for your resources. You are advised to create predefined tags in TMS. For details, see Creating Predefined Tags.
If your organization has configured tag policies for Cloud Eye, follow the policies when configure Tag for an alarm rule. If the tag configured does not comply with the tag policies, alarm rules may fail to be created. In this case, you can contact your administrator to learn more about the tag policies.
- A key can contain up to 128 characters, and a value can contain up to 225 characters.
- You can create up to 20 tags.
- Click Create.
- Set the alarm rule name and description.
After the alarm rule is created, if the metric data reaches the specified threshold, Cloud Eye immediately informs you that an exception has occurred.
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