tencent cloud

Note

Tencent Prometheus Service (TPS) has been integrated into TMP, which supports cross-region monitoring in multiple VPCs, and provides a unified Grafana dashboard, allowing for checking of multiple monitoring instances. For more information on TMP billing, see Pay-as-You-Go. For cloud resource usage details, see Billing Mode and Resource Usage. Free metrics for basic monitoring will not be billed.

TPS will be discontinued on May 16, 2022,see Announcements. Click here to try out TMP. TPS instances can no longer be created, but you can use our quick migration tool to migrate your TPS instances to TMP. Before the migration, streamline monitoring metrics or reduce the collection frequency; otherwise, higher costs may be incurred.

Overview

This document describes how to configure alarm policies in cloud native monitoring.

Prerequisites

Before configuring alarm policies, you need to perform the following operations:

• You've created a TMP instance.
• The cluster to be monitored has been associated with the corresponding instance as instructed in Associating with Cluster.
• The information that needs to be collected has been added to the data collection configuration of the cluster.

Directions

Configuring alarm policies

1. Log in to the TKE console and click Cloud Native Monitoring in the left sidebar.
2. On the instance list page, select the target instance to enter its details page.
3. On the Alarm configurations page, click Create alarm policy.
   
4. On the Create alarm policy page, add the details of the alarm policy.
   

• Rule name: Name of alarm rule (up to 40 characters).
• PromQL: Alarm rule statement.
• Duration: When the condition described in the above statement reaches the duration specified here, an alarm will be triggered.
• Label: Prometheus labels of each rule.
• Alarm content: The alarm notifications to be sent to recipients through email and SMS when an alarm is triggered.
• Convergence time: In this specified period, if the alarm condition is met multiple times, only one notification is sent.
• Effective time: Alarm notifications can only be sent during the effective period.
• Recipient group: Notifications will be sent to the specified contact group.
• Delivery method: The delivery channel of alarm notifications.

6. Click Complete.

   Note：

   The alarm policy will take effect by default once created.

Pausing alarming

1. Log in to the TKE console and click Cloud Native Monitoring in the left sidebar.
2. On the instance list page, select the target instance to enter its details page.
3. On the Alarm configurations page, click More > Pause alarming on the right side of the instance.
   
4. In the Disable alarm policy pop-up window, click OK.