Creating an Alarm Rule to Monitor a Server

Scenarios

This topic describes how to create an alarm rule to monitor an ECS or BMS.

Procedure

1. Log in to the management console.
2. In the upper left corner, select a region and project.
3. Choose Service List > Cloud Eye.
4. In the navigation pane, choose Server Monitoring.
5. Locate the target ECS or BMS. In the Operation column, choose More > Create Alarm Rule.
6. On the Create Alarm Rule page, configure the parameters.
   1. 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.

   2. Select resources and configure other parameters.

      Table 2 Parameter description

      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
      Dimension	Specifies the metric dimension of the selected resource type.	ECSs
      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: 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. NOTE: 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

   3. Configure the alarm notification.

      Table 3 Alarm Notification parameters

      Parameter	Description
      Alarm Notification	Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, SMS 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: 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	Specifies the 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.

   4. 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 who have all permissions for the enterprise project can manage the alarm rules. 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.

   5. Click Create.