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 Replica 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

Glossary

Enabling Event Alarms

PDF

Modo Foco

Tamanho da Fonte

Última atualização: 2025-11-20 09:44:42

TencentDB for PostgreSQL supports the event alarm feature. If the user sets event alarms related to CPU elastic scaling and configures alarm notifications, when events such as scale-out triggering, scale-out failure, and scale-in are detected, event alarm notifications will be sent through various optional channels to the user. This document introduces how to set up event alarms related to CPU elastic scaling.
Scenarios
Users can create event alarms to trigger alarms and send related messages when status changes (such as CPU elastic scale-out success, CPU elastic scale-out failure, and CPU elastic scale-in success) occur after the elastic scaling feature is enabled in TencentDB for PostgreSQL.
Operation Steps
Creating an Alarm Policy
1. Log in to the Tencent Cloud Observability Platform console, and choose Alarm Management > Alarm Configuration in the left sidebar.
2. On the alarm policy page, select Cloud Product Monitoring as the monitoring type and click Create Policy.
3. On the policy creation page, complete the settings for basic information, alarm rules, and alarm notifications.
Policy Type: Choose Cloud Database > PostgreSQL.
Alarm Object: You can find the object instance that needs to be associated by selecting the region where the object is located or searching for the instance ID of the object.
Trigger Condition: Find event alarms, click Add Event, and add CPU performance scale-out, CPU performance scale-out failure, and CPU performance scale-in alarm events respectively.
﻿
Configure alarm notification: You can select a preset or user-defined notification template. For custom notification templates, see Creating Notification Template.
Select a system preset template.
﻿
Create a template.
﻿
4. After confirmation, click Complete.
Associating an Alarm Object
After creating an alarm policy, you can also associate it with other alarm objects (instances that require alarms related to the CPU performance scaling). When the object meets the alarm trigger condition, an alarm will be sent.
1. On the Alarm Policy page, click the Policy Name to enter the alarm policy management page.
2. On the Alarm Object 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.