Configure Alarm Policy

You can create alarms to trigger alarms when the cloud service status reaches the set conditions and send relevant messages to specified user groups. The created alarm will determine whether to trigger relevant notifications based on the situation of the monitored metrics relative to the given threshold at intervals.

When a cloud service status change causes an alarm to be triggered, designated users can take corresponding preventive or remedial measures in a timely manner. Therefore, creating alerts properly can help you improve the robustness and reliability of your application. For more information about alarms, see Create an alarm policy.

The detailed steps to create an alarm policy are as follows:

1. Log in to the cloud console and click Cloud Monitor to enter the cloud monitor console.
2. On the left menu, select Alarm Configuration > Alarm Policy to enter the alarm policy configuration page.
3. Click Add to configure the alarm policy.
4. For Configuring basic options, the configuration instructions are as follows.

• Policy Name: Enter the policy name.
• Notes: Fill in the policy notes.
• Policy Type: Select a monitoring item.

5. Configure the alarm object.

• After you select all objects, the alarm policy is bound to all instances under the current account.
• After you select some objects, the alarm policy is bound to the instances selected.
• By selecting an instance group, the alarm policy will be bound to the user-selected group of instances.

6. Set the alarm trigger conditions. There are two methods: trigger condition template and configure trigger condition. You can choose one of the trigger conditions.

• Trigger Condition Template
  Open the trigger condition template and select a configured template from the drop-down list. For detailed configuration, see the Cloud Monitor documentation. If the newly created template is not displayed, click Refresh on the right to refresh the trigger alarm template selection list.
• Configure Trigger Condition
  The alarm trigger condition is a semantic condition composed of metrics, statistical cycles, comparison relationships, thresholds, duration cycles, and repeated notifications.
  For example, if the specified metric is the number of packets, the statistical period is one minute, the comparison relationship is >, threshold is 100 per second, the duration is for 2 cycles, repeat notification is once every day, this indicates: The incoming packet data is collected once every minute; if the incoming packet volume of a CLB instance listener exceeds 100 packets per second for two consecutive times, an alarm is triggered, and once daily.

7. Configure Alarm Channels
   Configure the alarm receiving group, effective period, and receiving channel (email, object) as required.

8. You can set an existing policy as the default alarm policy, and newly purchased CLB will be automatically associated with the default policy.

• There is only one default policy per project for each policy type.
• The default alarm policy cannot be deleted.