Managing Alarm Triggering Policies

Last updated: 2020-02-11 19:47:25



AS supports the dynamic scaling of the number of instances in a scaling group based on monitoring metrics, provided that you define the alarm trigger policy, including the status of the monitoring metrics that trigger the scaling, and how you want to scale in response to changing demand.

You need to specify the conditions and actions when creating an alarm policy:

  • Condition format: A metric + Threshold + Period + Number of periods during which the threshold is reached. That is, the value of the metric breaches the threshold that you defined, for the number of periods that you specified.
  • Execution actions: Sending notification(s) + adding/removing CVMs according to the specified number

We recommended you create two policies for each scaling group, one for scale-out and one for scale-in. Once the traffic to your web application reaches the threshold of the alarm policy, AS executes the associated policy to scale your group in (by terminating instances) or out (by launching instances).

This is shown in the following figure:


For example, you have an e-commerce web application that currently runs on five instances. You plan to carry out an operational activity, and are concerned that the access traffic is much greater than you had expected. You can configure a scaling group to add two new instances when the load on the current instance reaches 70%, and terminate extra instances when the load decreases to 40%.


  1. Open the Console, and select Scaling Group in the navigation bar.

  2. Select the scaling group to be modified, and click the Scaling Group ID to enter the basic scaling group information page.

  3. Select Alarm Trigger Policy in the top navigation bar, and manage the alarm trigger policy associated with the scaling group on this page.

    • Click Create to add a new alarm trigger policy.
    • Click Delete to delete the alarm trigger policy.

Preventing specified CVMs from being removed by the scaling policy

For the proper running of your existing business, if the CVMs in the cluster are used for the following purposes, you need to prevent them from being removed by the scale-in policy:

  • Multiple purposes: Apart from the tasks specified by the cluster, a CVM in the cluster is also used for other purposes, for example the CVM is used as both a cache server and a file server.

  • Data storage: The CVM is stateful or stores data that other CVMs do not have. For example, the CVM stores the incremental data of other running CVMs in a cluster.

  • Image/Snapshot updates: The CVM is used to regularly update images and snapshots.


Step 1: In the Scaling Group List, click the scaling group to which the CVM belongs to go to the management page.

Step 2: In the CVM List at the bottom of the management page, click Enable removal protection for the CVM.