tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us

Setting Alarm Notification

PDF
Focus Mode
Font Size
Last updated: 2025-12-29 14:40:59
After setting an alarm policy, you need to add alarm recipients, which can be done during alarm notification configuration.
This document describes how to set an alarm notification template in the console. When creating an alarm policy on the alarm policy configuration page, you can select an existing template or create a new one for easy configuration. You can also quickly apply the same template for multiple policies.
For more information on relevant limits and other descriptions, see Creating Notification Template.

Setting an alarm notification template

1. Log in to the TCOP console and select Notification Template on the left sidebar.
2. Click Create Notification Template, configure the following items on the page displayed, and click Complete.


Parameter
Description
Template Name
Enter the notification template name, which can contain up to 30 characters.
Notification Type
Select one or multiple notification types. Options include Alarm Trigger and Alarm Recovery.
Notification Language
Select the notification language, which can be Chinese or English.
Recipient Object
Select users or user groups to receive notifications.
Notification Cycle
Select the notification cycle, which can be any number of days in a week.
Notification Period
Set the notification period. Alarm notifications will be sent at the start time in the notification cycle and will be stopped at the end time.
Receiving Channel
Select email, SMS, etc.
API URL
Enter a URL (domain name or IP[:port][/path]), WeCom group chatbotwebhook, DingTalk group chatbot webhook, or Slack group application webhook accessible over the public network, and TCOP will push alarm messages to the corresponding URL, WeCom group, DingTalk group, or Slack group (if the recipient is a user, there is no need to add an API callback).
Note:
You need to enter the API callback only when pushing notifications to WeCom group chatbots, DingTalk group chatbots, or Slack group applications.
After the API callback is added, if the initial delivery of an alarm notification fails, CM attempts up to three retries with a delay between failed attempts set at 5 seconds.
After the API callback is added, each WeCom or DingTalk group chatbot can receive up to 20 notifications per minute. If this quota is exceeded, the excess notifications will be discarded for WeCom, and the traffic will be throttled for 10 minutes for DingTalk.

Configuring an alarm notification

1. Log in to the TCOP console and select Policy Management on the left sidebar.
2. Click Create Policy and select up to three alarm notification templates in Configure Alarm Notification in the Configure Alarm Policy window.
3. Click Complete after configuring the alarm policy and notification.



4. After the configuration is completed, if an alarm is triggered by an exception, the system will send notifications to the recipients via the specified channels (email, SMS, WeCom, and phone call).

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback