tencent cloud

TencentDB for PostgreSQL

Release Notes and Announcements
Release Notes
Product Announcements
Product Introduction
Overview
Features
Strengths
Scenarios
Information Security
Regions and AZs
Product Feature List
Large version lifecycle description
MSSQL Compatible Version
Billing
Billing Overview
Instance Type and Specification
Purchase Methods
Refund
Overdue Payments
Backup Space Billing
Database Audit Billing Overview
Getting Started
Creating TencentDB for PostgreSQL Instance
Connecting to TencentDB for PostgreSQL Instance
Managing TencentDB for PostgreSQL Instance
Importing Data
Migrating Data with DTS
Kernel Version Introduction
Kernel Version Overview
Kernel Version Release Notes
Viewing Kernel Version
Proprietary Kernel Features
Database Audit
Audit Service Description
Activating Audit Service
View Audit Logs
Modify audit services
Audit Performance Description
User Guide
Instance Management
Upgrading Instance
CPU Elastic Scaling
Read-Only Instance
Account Management
Database Management
Parameter Management
Log Management and Analysis
Backup and Restoration
Data Migration
Extension Management
Network Management
Access Management
Data Security
Tenant and Resource Isolation
Security Groups
Monitoring and Alarms
Tag
AI Practice
Using the Tencentdb_ai Plug-In to Call Large Models
Building Ai Applications with the Tencentdb Ai Plug-In
Combining Supabase to Quickly Build Backend Service Based on TencentDB for PostgreSQL
Use Cases
postgres_fdw Extension for Cross-database Access
Automatically Creating Partition in PostgreSQL
Searching in High Numbers of Tags Based on pg_roaringbitmap
Querying People Nearby with One SQL Statement
Configuring TencentDB for PostgreSQL as GitLab's External Data Source
Supporting Tiered Storage Based on cos_fdw Extension
Implement Read/Write Separation via pgpool
Implementing Slow SQL Analysis Using the Auto_explain Plugin
Using pglogical for Logical Replication
Using Debezium to Collect PostgreSQL Data
Set Up a Remote Disaster Recovery Environment for PostgreSQL Locally on CVM
Read-Only Instance and Read-Only Group Practical Tutorial
How to Use SCF for Scheduled Database Operations
Fix Table Bloat
Performance White Paper
Test Methods
Test Results
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Read-Only Instance APIs
Backup and Recovery APIs
Parameter Management APIs
Security Group APIs
Performance Optimization APIs
Account APIs
Specification APIs
Network APIs
Data Types
Error Codes
FAQs
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us
DokumentasiTencentDB for PostgreSQLUser GuideMonitoring and AlarmsAlarming Feature

Alarming Feature

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-03-31 10:43:39

Scenarios

The alarm feature is used to trigger alarms and send relevant messages when the cloud database status changes. Created alarms will determine whether to trigger relevant notifications based on the metrics monitored at regular intervals relative to given thresholds.
After a status change triggers an alarm, you can take timely preventive or remedial measures. Therefore, reasonably creating alarms can help you improve the robustness and reliability of your applications. For more information about alarms, see the Alarm Configuration in TCOP.
When a user needs to send an alarm for a specific product status, they must first create an alarm policy. An alarm policy consists of three essential components: name, type, and alarm trigger conditions. Each alarm policy is a collection of alarm trigger conditions in an "OR" relationship, meaning an alarm is sent if any single condition is met. Alarms will be sent to all recipients associated with the policy. After receiving the alarm, users can promptly review it and take corresponding actions.
Note:
Please ensure that you have set the default alarm recipient; otherwise, the default alarm policy for Tencent Cloud cloud database will not notify you.

Operation Steps

Creating an Alarm Policy

1. Log in to the TCOP console, and choose Alarm Management > Alarm Configuration in the left sidebar.
2. On the alarm policy list page, click Create Policy.
3. On the New Policy page, configure the policy name, policy type, alarm objects, trigger conditions, and other settings.
An alarm trigger condition is a semantic condition composed of a metric, comparison operator, threshold, statistical period, and duration period. For example, configure a trigger condition: metric is disk utilization, comparison operator is >, threshold is 80%, statistical period is 5 minutes, duration period is 2 periods. This means: TCOP collects disk utilization data every 5 minutes. If the disk utilization of a cloud database exceeds 80% for two consecutive times, then an alarm is triggered.
You can locate the object instance to be associated by selecting the region where the object resides or searching for the Instance ID of the object.
4. After confirmation, click Complete to finish.

Associating an Alarm Object

After an alarm policy is created, you can associate it with alarm objects. When objects meet the alarm trigger conditions, alarms will be sent.
1. On the alarm policy list page, click the alarm policy name to go to the alarm policy management page.
2. On the "Alarm Objects" section of the alarm policy management page, click Add Object.

3. In the pop-up dialog box, select the alarm object to be associated with, and click OK to associate the alarm object.
Topik sebelumnya: Monitoring FeatureTopik selanjutnya: Overview

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan