tencent cloud

Feedback

Setting Alarm Policies

Last updated: 2022-05-11 14:25:41

    Overview

    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.

    Note:

    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, see Creating Alarm Policy.

    Directions

    1. Log in to the COS console. On the Overview page, click Configure Alarm Policy in the Alarm Configuration section.
      Note:

      Alarm Configuration can also be found on the Overview page of each bucket.

    2. Click Create and configure a new alarm policy as shown below:
      Configuration Type Configuration Item Description
      Basic Information Policy Name Custom policy name.
      Remarks Custom policy remarks.
      Monitor Type Select **Cloud Product Monitoring**.
      Policy Type Select **COS**.
      Project 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 select 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, 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, see Cloud Access Management (CAM) for authorization.
      Configure Alarm Rule Alarm Object
      • If you select **Instance ID** from the drop-down list, select the bucket you want to add an alarm to.
      • If you select **Instance Group** from the drop-down list, the alarm policy will be 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 select **All Objects** from the drop-down list, the alarm policy will be bound to all buckets the current account has permission for.
      Select template Select a configured template from the drop-down list. For more information on the configuration, see Configuring Trigger Condition Template. If the newly created template is not displayed, click Refresh on the right.
      Manual Configuration
      (Metric alarm)
      • **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 five minutes, and if the number of STANDARD storage read requests in a bucket is greater than 80 in two 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.
        Valid values: Do not repeat; Once every 5 minutes; Once every 10 minutes; At an exponentially increasing interval; 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.
      Configure Alarm Notification Alarm Notification Select a preset or custom notification template. Each alarm policy can be bound to three notification templates at most. For more information, see Cloud Monitor.
      Advanced Settings Auto Scaling If enabled, the auto scaling policy can be triggered when the alarm condition is met.
    3. After configuring the above information, click Save.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support