Creating an Alarm Rule
This topic describes how to create an alarm rule.
Creating an Alarm Rule
- Log in to the management console.
- Click Service List in the upper left corner and select Cloud Eye.
- In the navigation pane, choose Alarm Management > Alarm Rules.
- Click Create Alarm Rule in the upper right corner.
- On the Create Alarm Rule page, configure parameters.
- Set Name and Description.
Figure 1 Setting Name and Description
- Configure an alarm rule.
Figure 2 Configuring an alarm rule
Table 2 Alarm rule parameters Parameter
Description
Example Value
Alarm Type
Specifies the alarm type to which the alarm rule applies. The type can be Metric or Event.
Metric
Cloud Product
This parameter is only available if Metric is selected for Alarm Type. Select a cloud product from the drop-down list. For details about supported cloud products and their metrics, see Services Monitored by Cloud Eye.
Elastic Cloud Server - ECSs
Resource Level
This parameter is only available if Metric is selected for Alarm Type. Two options are available: Cloud product (recommended) and Specific dimension.
Take ECS as an example. ECSs is the cloud product. Specific dimensions are disks, mount points, processes, and more.
Cloud product
Monitoring Scope
This parameter is only available if Metric is selected for Alarm Type. Three options are available: All resources, Resource groups, or Specified resources.
NOTE:- 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.
- Resource groups: An alarm will be triggered if any resource in the to-be-selected resource group meets the alarm policy.
- Specified resources: Click Select Specific Resources to select resources.
All resources
Group
This parameter is available only if Metric is selected for Alarm Type and Resource groups for Monitoring Scope.
N/A
Instance
This parameter is available only if Metric is selected for Alarm Type and Specific resources for Monitoring Scope.
N/A
Threshold Type
For ECSs, you can select Static or Dynamic. The feature is available only in the CN South-Guangzhou region.
- Static: Indicates the fixed value set in an alarm rule. If the fixed value is reached, an alarm will be triggered.
- Dynamic: Indicates the predicative value range calculated based on historical data. If the current metric data deviates from the predicted value range, an alarm will be triggered.
Static
Event Type
This parameter is only available if Event is selected for Alarm Type. You can select either System event or Custom event.
System event
Event Source
This parameter is only available if Event is selected for Alarm Type.
- If System event is selected for Event Type, select the cloud service from which the event comes.
Example value: Elastic Cloud Server
- If Custom event is selected for Event Type, the event source must be the same as that of the reported fields and written in the service.item format.
N/A
Method
Configure manually: If Event is selected for Alarm Type and Custom Event for Event Type, Method is set to Configure manually by default.
Associate template: After an associated template is modified, the policies contained in this alarm rule to be created will be modified accordingly.
Configure manually
Template
You need to select a default template in either of the following conditions:
- Metric is selected for Alarm Type and Associate template is selected for Method.
- Event is selected for Alarm Type, System event is selected for Event Type, and Associate template is selected for Method.
You can also customize an alarm template.
N/A
Alarm Policy
If Event is selected for Alarm Type and Custom event is selected for Event Type, you need to set Alarm Policy.
If Custom event is selected for Event Type, as long as an event occurs, an alarm will be triggered. If there is an event, such as improper ECS running, Cloud Eye triggers an alarm. For details, see Alarm Policies.
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 will be triggered.
N/A
Alarm Severity
Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.
Major
- Configure the alarm notification.
Figure 3 Alarm Notification
Table 3 Alarm Notification parameters Parameter
Description
Alarm Notification
Specifies whether to send notifications to users over different protocols, such as SMS, email, voice notification, HTTP, HTTPS, FunctionGraph (function), FunctionGraph (workflow), WeCom chatbot, DingTalk chatbot, Lark chatbot, and WeLink chatbot.
Notification Type
The following three options are available:
- Notification policies: Flexible alarm notifications by severity and more notification channels are provided.
- Notification groups: Configure notification templates on Cloud Eye.
- Topic subscriptions: Configure notification templates on SMN.
Notification Policies
If Notification policies is selected for Notification Recipient, you need to select one or more notification policies. You can specify the notification group, window, template, and other parameters in a notification policy. For details, see Creating, Modifying, or Deleting a Notification Policy.
Notification Group
If Notification groups is selected for Notification Recipient, select the notification groups to which alarm notifications will be sent.
Notification Object
Specifies the object to which alarm notifications will be sent. You can select the account contact or a topic name. This parameter is available only if Topic subscriptions is selected for Notification Recipient.
- Account contact: Enter the 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 Template
This parameter is only available if Notification groups or Topic subscriptions is selected for Notification Recipient. You can select an existing template or create a new one.
Notification Window
This parameter is only available if Notification groups or Topic subscriptions is selected for Notification Recipient.
Specifies the time window during which Cloud Eye sends notifications.
If Notification Window is set to 08:00-20:00, Cloud Eye sends notifications only within this window.
Trigger Condition
This parameter is only available if Notification groups or Topic subscriptions is selected for Notification Recipient.
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.
- Select an enterprise project and set Tag.
Figure 4 Advanced Settings
Table 4 Enterprise Project and Tag 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 manage the alarm rule. For details about how to create an enterprise project, see Creating an Enterprise Project.
Tag
Specifies a key-value pair. Tags identify cloud resources so that you can easily 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 you add a tag that does not comply with the tag policies, alarm rules may fail to be created. Contact your administrator to learn more about 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 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.
To view monitoring graphs, click View Graph or View Resource in the Operation column, and click View Graph in the displayed View Resource dialog box.
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