Creating an Alarm Rule to Monitor a Server
To monitor the usage of cloud product resources, you can create alarm rules and configure alarm notifications. In this way, you will be notified immediately after the set thresholds are reached. This topic describes how to create an alarm rule to monitor an ECS or BMS.
Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Choose Service List > Cloud Eye.
- In the navigation pane, choose Server Monitoring > Elastic Cloud Server (or Bare Metal Server).
- Locate the target ECS or BMS. In the Operation column, choose More > Create Alarm Rule.
- On the Create Alarm Rule page, configure the parameters.
- Configure the alarm rule name, description, and associated enterprise project.
Table 1 Parameter description Parameter
Description
Name
Specifies the alarm rule name. The system generates a random name, which you can modify.
Description
(Optional) Provides supplementary information about the alarm rule.
- Select resources and configure other parameters.
Table 2 Parameter description Parameter
Description
Example Value
Alarm Type
Specifies the alarm type that the alarm rule applies to. The default value is Metric.
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
Specifies the monitoring scope the alarm rule applies to.
Specific resources
Monitored Object
You do not need to set the monitored object because it is the current ECS.
N/A
Method
- Configure manually: You can customize an alarm policy as needed. For details, see Alarm Policies.
- Associate template: If the same alarm rule needs to be configured for multiple groups of resources under the same cloud product, you can use an alarm template to simplify operation.
NOTE:
After an associated template is modified, the policies contained in this alarm rule to be created will be modified accordingly.
- When Resource Level is set to Cloud product, only changes to policies for the specified cloud product in an associated template will be automatically synchronized.
- When Resource Level is set to Specific dimension, only changes to policies for the specified dimension in an associated template will be automatically synchronized.
For example, if Resource Level is set to Specific dimension > ECSs, only changes to the ECS policies in the template will be automatically synchronized to the alarm rule, but changes to the policies of ECS disks will not.
Create manually
Template
Specifies the template to be used. This parameter is mandatory when Method is set to Associate template.
You can select a default alarm template or a custom template.
N/A
Alarm Policy
Specifies the policy for triggering an alarm.
For example, an alarm is triggered if the average CPU usage of the ECS is 80% or more for three consecutive 5-minute periods. Cloud Eye triggers an alarm every one hour again if the alarm persists.
For details about basic and OS monitoring metrics, see Cloud Product Metrics.
NOTE:- That is, if the alarm is not cleared after it is generated, an alarm notification is sent, once every hour.
- 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.
Table 3 Alarm Notification parameters Parameter
Description
Alarm Notification
Whether to send SMS messages, emails, FunctionGraph (function), FunctionGraph (Workflow), WeCom, DingTalk, Lark, WeLink or HTTP or HTTPS requests to users.
Notification Recipient
The following options are available:
- Notification group: Configure notification templates on Cloud Eye.
- Topic subscription: Configure notification templates on SMN.
Notification Group
Specifies the notification group for receiving alarm notifications. For details, see Creating a Notification Object and Notification Group.
Notification Object
Specifies the object to which alarm notifications will be sent. You can select the account contact or a topic.
- Account contact: Enter the phone number and email address of the registered account.
- Topic: A topic is used to publish messages and subscribe to notifications. If the required topic is unavailable, create one and add subscriptions to it on the SMN console. For details, see Creating a Topic and Adding Subscriptions. For the HTTP/HTTPS messages, see HTTP/HTTPS Messages.
Validity Period
Cloud Eye sends notifications only within the notification window specified in the alarm rule.
If Validity Period is set to 08:00-20:00, Cloud Eye sends notifications only from 08:00 to 20:00.
Trigger Condition
Condition that will trigger an 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 1 Advanced Settings
Table 4 Parameters of Advanced Settings Parameter
Description
Enterprise Project
Specifies the enterprise project that the alarm rule belongs to. Only users with the enterprise project permissions can manage the alarm rule. For details, see Creating an Enterprise Project.
Tag
A tag is 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 you have configured tag policies for Cloud Eye, add tags to alarm rules based on the tag policies. 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 a maximum of 128 characters, and a value can contain a maximum of 225 characters.
- A maximum of 20 tags can be added.
- Click Create.
- Configure the alarm rule name, description, and associated enterprise project.
After the alarm rule is created, if the metric 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