You can leverage the alarm policy feature of Cloud Monitor to set threshold-reaching alarms for COS monitoring metrics. An alarm policy must include the policy name, policy type, trigger condition, alarm object, and alarm notification template. You can create an alarm policy for COS as instructed below.
Tencent Cloud’s Cloud Monitor enables users to monitor cloud resources in real time and provides alarm services. Users can set alarm policies for COS monitoring metrics to query the alarm history and receive alarm notifications. For more information, please see Creating Alarm Policy.
Log in to the COS console. On the Overview page, click Configure Alarm Policy in the Alarm Configuration area.
Alarm Configuration can also be found on the Overview page of each bucket.
Click Create on the page that is displayed and configure an alarm policy. The configuration items are as follows:
| Basic info
||User-defined policy name
||User-defined remarks for the policy
||Choose Cloud Product Monitoring.
||Setting the policy project allows you to:|
- Manage alarm policies. Alarm policies of a project can be quickly located in the alarm policy list.
- Manage instances. You can choose the project as needed. Instances of the project can be quickly located in Alarm Object. You can distribute Tencent Cloud services to the desired project according to your business types. To create a project, please see Project Management. After the project is created, you can distribute resources to projects in the console of each Tencent Cloud service. Some Tencent Cloud services cannot be distributed to a project. If you do not have project permission, please see Cloud Access Management (CAM) for authorization.
|Configure alarm rule
- If you choose Instance ID in the drop-down list, select the bucket you want to add an alarm to.
- If you choose Instance Group in the drop-down list, the alarm policy is bound to the selected instance group. If there is no instance group, you can click Create Instance Group on the right to create a group for the bucket first.
- If you choose All Objects in the drop-down list, the alarm policy is bound to all buckets the current account has permission on.
(choosing Manual Configuration)
- Trigger condition: consists of metric, comparison, threshold, statistical period, and the number of consecutive periods.
For example, if the metric is set to `STANDARD storage read requests`, comparison to `>`, threshold to `80` times, statistical period to `5` minutes, and the number of consecutive periods to `Last 2 periods`,
STANDARD storage read requests are collected every 5 minutes, and if the number of STANDARD storage read requests in a bucket is greater than 80 in 2 consecutive periods, the alarm will be triggered.
- Alarm frequency: you can set a repeated notification policy for each alarm rule. In this way, an alarm notification will be sent repeatedly at a specified frequency when an alarm is triggered.
Frequency options: do not repeat, once every 5 minutes, once every 10 minutes, at an exponentially increasing interval, and other frequency options.
- An exponentially increasing interval means that a notification is sent when an alarm is triggered the 1st time, 2nd time, 4th time, 8th time, and so on. In other words, the alarm notification will be sent less and less frequently as time goes on to reduce the disturbance caused by repeated notifications.
- Default logic for repeated alarm notifications: the alarm notification will be sent to you at the configured frequency within 24 hours after the alarm is triggered. After 24 hours, the alarm notification will be sent once a day by default.
|Trigger condition (choosing Select template)
||Select a configured template in the drop-down list. For more information about the configurations, please see Configuring trigger condition templates. If the newly created template is not displayed, click the Refresh icon on the right.
|Configure alarm notification
||You can select a preset notification template or customize one. Up to 3 notification templates can be bound to each alarm policy.
||If enabled, the auto scaling policy can be triggered when the alarm condition is met.