Creating an Alarm Rule

Creating an Alarm Rule

1. Log in to the management console.
2. Click Service List in the upper left corner and select Cloud Eye.
3. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
4. Click Create Alarm Rule in the upper right corner.
5. On the Create Alarm Rule page, follow the prompts to configure the parameters.
   1. Configure 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.

   2. Select a monitored object and configure alarm content parameters.

      Table 2 Parameters

      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. You can select Resource groups or Specific resources. NOTE: 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.	Specific resources
      Group	This parameter is mandatory when Monitoring Scope is set to Resource groups.	N/A
      Method	There are two options: Use template or Configure manually.	Configure 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 an alarm will be triggered 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
      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 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 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 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.

After the alarm rule is created, if the metric data reaches the specified threshold, Cloud Eye immediately informs you that an exception has occurred.