Creating an Alarm Rule to Monitor a Server

Scenarios

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

Procedure

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

      Table 2 Parameter description

      Parameter	Description	Example Value
      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	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.	Configure manually
      Template	Specifies the template to be used. 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 monitored object 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 Services Interconnected with Cloud Eye. 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
      Mount Point or Disk	This parameter is mandatory when the metric is a fine-grained disk metric. For the Windows OS, enter a drive letter, such as C, D, or E. For the Linux OS, enter a mount point, such as /dev or /opt.	/dev
      Alarm Severity	Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.	Major

   3. Configure the alarm notification.

      Table 3 Parameter description

      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 is the mobile 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 the Simple Message Notification User Guide.
      Validity Period	Cloud Eye sends notifications only within the validity period 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 for triggering an alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.

   4. Click Create.