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, configure required parameters.
   1. Set 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
      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. You can select All resources, Resource groups, or Specified resources. NOTE: If you select All resources, an alarm will be triggered when any instance meets an alarm policy, and existing alarm rules of the current resource type and dimension will be automatically applied to newly purchased resources of the same resource type and dimension. If you select Resource groups, an alarm will be triggered when any resource in the group meets the alarm policy. If you select Specific resources, select one or more resources and click to add them to the box on the right.	All resources
      Method	You can select an associated template, use an existing template or create a custom template as required. 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 customize an alarm 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 to trigger an alarm 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 operation. For example, if event improper ECS running occurs, Cloud Eye triggers an alarm. For details, see Alarm Policies. 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
      Alarm Severity	Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.	Major

   3. Configure the alarm notification.
      Figure 1 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 or text message, or by HTTP/HTTPS request to servers.
      Notification Type	You can select a notification group or topic subscription as required.
      Notification Group	Specifies the notification group to which alarm notifications will be sent.
      Notification Object	Specifies the object that receives alarm notifications. You can select the account contact or a topic. Account contact is the phone 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.
      Notification Window	Cloud Eye sends notifications only within the notification window you specified. If Notification Window is set to 08:00-20:00, Cloud Eye sends notifications only within 08:00–20:00.
      Trigger Condition	Specifies the condition for triggering the alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.

   4. Configure Enterprise Project and Tag.
      Figure 2 Advanced Settings
      

      Table 4 Configuring Enterprise Project and Tag

      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 rule. For details about how to create an enterprise project, see Creating an Enterprise Project.
      Tag	Specifies 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 your organization has configured tag policies for Cloud Eye, follow the policies when configure Tag for an alarm rule. 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 up to 128 characters, and a value can contain up to 225 characters. You can create up to 20 tags.

   5. 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.

To view monitoring graphs, click View Graph or View Resource in the Operation column, and click View Graph in the displayed View Resource dialog box.