Modifying an Alarm Rule

Procedure

1. Log in to the management console.
2. Click Service List in the upper left corner and select Cloud Eye.
3. Choose Alarm Management > Alarm Rules.
4. On the displayed Alarm Rules page, use either of the following two methods to modify an alarm rule:
   • Locate the row containing the alarm rule you want to modify, click Modify in the Operation column.
   • Click the name of the alarm rule you want to modify. On the page displayed, click Modify in the upper right corner.
5. On the Modify Alarm Rule page, modify alarm rule parameters as needed.

   Table 1 Parameters

   Parameter	Description	Example Value
   Name	Specifies the alarm rule name. The system generates a random name, which you can modify.	alarm-b6al
   Description	(Optional) Provides supplementary information about the alarm rule.	N/A
   Alarm Type	Specifies the alarm type to which the alarm rule applies.	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. You can select Resource groups or Specific resources. NOTE: When you set Monitoring Scope to Specific resources, you can add new monitored objects and remove the original monitored objects.	Specific resources
   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. NOTE: The last part of the alarm policy indicates how often to trigger an alarm again when the alarm has been triggered but the monitored object is still abnormal.	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
   Alarm Notification	Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, SMS message, or HTTP/HTTPS message.	N/A
   Notification Object	Specifies the object to which alarm notifications will be sent. You can select the account contact or a topic. The account contact is the tenant owner. If a user registers both a mobile number and an email address, they will receive alarm information through both channels. However, if only one of these contact methods is registered, the alarm information will be sent exclusively to that registered one. A topic is a specific event type for publishing messages or subscribing to notifications. If the required topic is not available, create one and add subscriptions to it first. For details, see Creating a Topic and Adding Subscriptions.	N/A
   Notification Window	Cloud Eye sends notifications only within the notification window specified in the alarm rule. If Notification Window is set to 00:00-08:00, Cloud Eye sends notifications only from 00:00 to 08:00.	N/A
   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.	N/A
   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 about how to create an enterprise project, see .	default

6. Click OK.