Creating Alarm Rules

Scenarios

You can set alarm rules and notifications for DCC to stay informed about its status and receive timely alarms.

This section describes how to set alarm rules.

Currently, Cloud Eye is available only in some regions for monitoring DCC. For details, see the management console.

Metrics

**Table 1** Alarm policies for DCC metrics
Metric	Normal Range	Alarm Policy	Approach Upper Limit	Metric Description and Alarm Handling
Host CPU Allocation Rate	0-100	Alarm threshold: Original value > 90% Consecutive triggering times: 3 Alarm severity: Critical	Yes	Metric description: CPU allocation rate of a host. Unit: %. Handling suggestion: If this alarm is generated, the available CPU resources of the host are less than 10%. You can purchase new hosts to expand the resource pool to prevent VM provisioning failures caused by insufficient resources.
Host Memory Allocation Rate	0-100	Alarm threshold: Original value > 90% Consecutive triggering times: 3 Alarm severity: Critical	Yes	Metric description: Memory allocation rate of a host. Unit: %. Handling suggestion: If this alarm is generated, the available memory resources of the host are less than 10%. You can purchase new hosts to expand the resource pool to prevent VM provisioning failures caused by insufficient resources.
Resource Pool CPU Allocation Rate	0-100	Alarm threshold: Original value > 90% Consecutive triggering times: 3 Alarm severity: Critical	Yes	Metric description: CPU allocation rate of a resource pool. Unit: %. Handling suggestion: If this alarm is generated, the available CPU resources of the resource pool are less than 10%. You can purchase new hosts to expand the resource pool to prevent VM provisioning failures caused by insufficient resources.
Resource Pool Memory Allocation Rate	0-100	Alarm threshold: Original value > 90% Consecutive triggering times: 3 Alarm severity: Critical	Yes	Metric description: Memory allocation rate of a resource pool. Unit: %. Handling suggestion: If this alarm is generated, the available memory resources of the resource pool are less than 10%. You can purchase new hosts to expand the resource pool to prevent VM provisioning failures caused by insufficient resources.

Procedure

Log in to the Console Eye console.
In the navigation pane, choose Alarm Management > Alarm Rules.
On the displayed Alarm Rules page, click Create Alarm Rule.
You can also select an existing alarm rule and modify it as needed.

Configure basic information of the alarm rule.

Figure 1 Alarm rule information
Click to enlarge

**Table 2** Basic parameters for the alarm rule
Parameter	Description	Example value
Name	Name of the alarm rule. The system generates a random name, and you can change it as needed.	alarm-cprn
Description	Description of the alarm rule. This parameter is optional.	-

Select an object to be monitored and configure alarm parameters.
Figure 2 Metric alarm configuration

Key parameters are described below. For details, see Creating an Alarm Rule and Notifications.
- Alarm Type: The type of the alarm that the alarm rule applies to. You can select Metric or Event.
- Resource Type: This parameter is only available if you select Metric for Alarm Type. Select the service you want to monitor from the drop-down list, for example, Dedicated Computing Cluster.
- Dimension: Select the resource level of the monitored object. Select Cluster or Host based on service requirements.
- Monitoring Scope: The scope that the alarm rule applies to. You can select All resources, Resource groups, or Specific resources.
- Method: Select Associate template or Configure manually.
  
  After an associated template is modified, the policies contained in this alarm rule to be created will be modified accordingly.
Set alarm notification parameters.
To send alarm notifications by email, SMS, HTTP, or HTTPS, enable Alarm Notifications.

For details about related parameters, see Creating an Alarm Rule and Notifications.
Click Create.

For more information about alarm rules, see Cloud Eye User Guide.