Creating an AS Policy

Scenarios

You can create different types of AS policies. In an AS policy, you can define the conditions for triggering a scaling action and what operation to be performed. When the conditions are met, AS automatically triggers a scaling action to adjust the number of instances in the AS group.

This section describes how to create alarm-based, scheduled, or periodic AS policies for AS groups.

Creating an Alarm Policy

1. Log in to the AS console.

2. Locate the row containing the target AS group and click View AS Policy in the Operation column.
3. On the AS Policies page, click Add AS Policy.
4. Set the parameters listed in Table 1.
   Figure 1 Creating an Alarm Policy
   

   Table 1 AS policy parameters

   Parameter	Description	Example
   Policy Name	Specifies the name of the AS policy to be created.	as-policy-p6g5
   Policy Type	Select Alarm.	Alarm
   Alarm Rule	Specifies whether a new alarm rule is to be created (Create) or an existing alarm rule will be used (Use existing). For details about how to use an existing alarm rule, see Setting Monitoring Alarm Rules. If you choose to create an alarm, system monitoring and custom monitoring are supported. System monitoring requires the parameters in Table 2. Custom monitoring requires the parameters in Table 3. NOTE: If you select Use existing, do not choose alarm rules that are: Used to monitor all resources. Created by associating templates.	Create
   Scaling Action	Specifies the scaling action to be executed and the number or percentage of instances. The following scaling action options are available: Add Adds instances to an AS group when the scaling action is performed. Reduce Removes instances from an AS group when the scaling action is performed. Set to Maintains a fixed number of instances in an AS group.	Add 1 instance Add 10% instances The number of instances to be added is 10% of the current number of instances in the AS group. If the product of the current number of instances and the percentage is not an integer, AS automatically rounds the value up or down: If the value is greater than 1, it is rounded down. For example, value 12.7 is rounded down to 12. If the value is greater than 0 but less than 1, it is rounded up to 1. For example, value 0.67 is rounded up to 1. For example, suppose that there are 10 instances in an AS group, and the scaling action is Add 15% instances. When the AS policy is triggered, AS calculates the number of instances to be added as 1.5 and rounds 1.5 down to 1. After the scaling action is complete, there are 11 instances in the AS group.
   Cooldown Period	To prevent an alarm-based policy from being repeatedly triggered by the same event, you can set a cooldown period. A cooldown period (in seconds) is the period of time between two scaling actions. AS recounts the cooldown period after a scaling action is complete. During the cooldown period, AS denies all scaling requests triggered by alarm-based policies. Scaling requests triggered manually or by scheduled or periodic policies are not affected. For example, suppose that the cooldown period is set to 300 seconds (5 minutes), and a scheduled policy is specified to trigger a scaling action at 10:32, and a previous scaling action triggered by an alarm policy ends at 10:30. Any alarm-triggered scaling action will then be denied during the cooldown period from 10:30 to 10:35, but the scaling action scheduled for 10:32 will still take place. If the scheduled scaling action ends at 10:36, a new cooldown period starts at 10:36 and ends at 10:41. NOTE: If a scaling action is triggered by an AS policy, the cooldown period configured for that AS policy applies. If a scaling action is triggered by manually changing the expected number of instances or by other actions, the cooldown period configured for the AS group applies. The default cooldown period is 300 seconds. When an AS group scales out, scale-in requests triggered manually or by scheduled or periodic policies will be executed immediately after the scale-out is complete, without being affected by the cooldown period. When an AS group scales in, scale-out requests triggered manually or by scheduled or periodic policies will be executed immediately after the scale-in is complete, without being affected by the cooldown period.	300s

   Table 2 System monitoring parameters

   Parameter	Description	Example
   Rule Name	Specifies the name of the alarm rule.	as-alarm-7o1u
   Monitoring Type	Specifies the type of monitoring metrics, which can be System monitoring or Custom monitoring. Select System monitoring.	System monitoring
   Trigger Condition	Select monitoring metrics supported by AS and set alarm conditions for the metrics.	CPU Usage Max. >70%
   Monitoring Interval	Specifies the interval at which the alarm status is updated based on the alarm rule.	5 minutes
   Consecutive Occurrences	Specifies the number of sampling points when an alarm is triggered. If Consecutive Occurrences is set to n, the sampling points of the alarm rule are the sampling points in n consecutive sampling periods. The alarm rule status does not change to Alarm unless all sampling points breach the threshold configured by the alarm rule.	3

   Table 3 Custom monitoring parameters

   Parameter	Description	Example
   Rule Name	Specifies the name of the alarm rule.	as-alarm-7o1u
   Monitoring Type	Select Custom monitoring. Custom monitoring meets monitoring requirements in various scenarios.	Custom monitoring
   Resource Type	Specifies the name of the service for which the alarm rule is configured.	AGT.ECS
   Dimension	Specifies the metric dimension of the alarm rule.	instance_id
   Instance	Specifies the resources to which the alarm rule applies.	-
   Trigger Condition	Select monitoring metrics supported by AS and set alarm conditions for the metrics.	CPU Usage Max. >70%
   Monitoring Interval	Specifies the interval at which the alarm status is updated based on the alarm rule.	5 minutes
   Consecutive Occurrences	Specifies the number of sampling points when an alarm is triggered. If Consecutive Occurrences is set to n, the sampling points of the alarm rule are the sampling points in n consecutive sampling periods. The alarm rule status does not change to Alarm unless all sampling points breach the threshold configured by the alarm rule.	3

5. Click OK.

   The newly added AS policy is displayed on the AS Policies tab. In addition, the AS policy is in Enabled state by default.

Creating a Scheduled or Periodic Policy

1. Log in to the AS console.

2. Locate the row containing the target AS group and click View AS Policy in the Operation column.
3. On the AS Policies page, click Add AS Policy.
4. Configure the parameters listed in Table 4.
   Figure 2 Creating a scheduled policy
   
   Figure 3 Creating a periodic policy
   

   Table 4 Parameter description

   Parameter	Description	Example
   Policy Name	Specifies the name of the AS policy to be created.	as-policy-p6g5
   Policy Type	Select Scheduled or Periodic for expanding resources at a specified time. If you select Periodic, you are required to configure two more parameters: Period Day Week Month Time Range Specifies the time range during which the AS policy can be triggered.	Day 2023/03/01 00:00:00 - 2023/03/31 23:59:59 In this example, the AS policy will trigger a scaling action every day in March, and will become invalid from April 1, 2023 00:00:00.
   Time Zone	The default value is GMT+08:00. GMT+08:00 is 8:00 hours ahead of Greenwich Mean Time.	GMT+08:00
   Triggered At	Specifies the time at which the AS policy is triggered. NOTE: The selected triggering time must fall inside the effective time range of the policy.	-
   Scaling Action	Specifies an action and the number of instances. The following scaling action options are available: Add Adds instances to an AS group when the scaling action is performed. Reduce Removes instances from an AS group when the scaling action is performed. Set to Sets the expected number of instances in an AS group to a specified value.	Add 1 instance Add 10% instances The number of instances to be added is 10% of the current number of instances in the AS group. If the product of the current number of instances and the percentage is not an integer, AS automatically rounds the value up or down: If the value is greater than 1, it is rounded down. For example, value 12.7 is rounded down to 12. If the value is greater than 0 but less than 1, it is rounded up to 1. For example, value 0.67 is rounded up to 1. For example, suppose that there are 10 instances in an AS group, and the scaling action is Add 15% instances. When the AS policy is triggered, AS calculates the number of instances to be added as 1.5 and rounds 1.5 down to 1. After the scaling action is complete, there are 11 instances in the AS group.
   Cooldown Period	To prevent an alarm-based policy from being repeatedly triggered by the same event, you can set a cooldown period. A cooldown period (in seconds) is the period of time between two scaling actions. AS recounts the cooldown period after a scaling action is complete. During the cooldown period, AS denies all scaling requests triggered by alarm-based policies. Scaling requests triggered manually or by scheduled or periodic policies are not affected. For example, suppose that the cooldown period is set to 300 seconds (5 minutes), and a scheduled policy is specified to trigger a scaling action at 10:32, and a previous scaling action triggered by an alarm policy ends at 10:30. Any alarm-triggered scaling action will then be denied during the cooldown period from 10:30 to 10:35, but the scaling action scheduled for 10:32 will still take place. If the scheduled scaling action ends at 10:36, a new cooldown period starts at 10:36 and ends at 10:41. NOTE: If a scaling action is triggered by an AS policy, the cooldown period configured for that AS policy applies. If a scaling action is triggered by manually changing the expected number of instances or by other actions, the cooldown period configured for the AS group applies. The default cooldown period is 300 seconds. When an AS group scales out, scale-in requests triggered manually or by scheduled or periodic policies will be executed immediately after the scale-out is complete, without being affected by the cooldown period. When an AS group scales in, scale-out requests triggered manually or by scheduled or periodic policies will be executed immediately after the scale-in is complete, without being affected by the cooldown period.	300s

5. Click OK.

   The newly added AS policy is displayed on the AS Policies tab. In addition, the AS policy is in Enabled state by default.

If you have created scheduled or periodic AS policies that are invoked at the same time, AS will execute the one created later. This constraint does not apply to alarm-triggered AS policies.

Related Documents

• If an AS group uses an alarm-based scaling policy, you can install the Agent on the instances to better monitor the AS group. To use Agent monitoring metrics, ensure that the Agent has been installed on the instances in the AS group. For details, see How Do I Install the Agent on Instances in an AS Group to Use Agent Monitoring Metrics?
• For details about the alarm triggering conditions supported by alarm policies, see What Are the Conditions to Trigger an Alarm-based AS Policy?
• For details about why a cooldown period is required, see What Is a Cooldown Period and Why Is It Required?