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 Policy

PDF
Focus Mode
Font Size
Last updated: 2025-12-29 14:22:58
This document describes how to create and manage an alarm policy in the console.

Overview

You can create alarm policies to trigger alarms and send alarm notifications when the TDSQL-C for MySQL status changes. The created alarm policies can determine whether an alarm needs to be triggered according to the difference between the monitoring metric value and the given threshold at intervals.
When the alarm is triggered by a status change, you can promptly take the necessary preventative or corrective action. Alarm policies can therefore, if appropriately created, help you improve the robustness and reliability of your database. For more information on alarms, see Creating Alarm Policy.
To send an alarm for a specific status of TDSQL-C for MySQL, you need to create an alarm policy at first. An alarm policy is composed of three compulsory components, that is, the name, type and alarm triggering conditions. Each alarm policy is a set of alarm triggering conditions with the logical relationship "OR", that is, as long as one of the conditions is met, an alarm will be triggered. The alarm will be sent to all users associated with the alarm policy. Upon receiving the alarm, the user can view the alarm and take appropriate actions in time. After creating an alarm policy, you can change its name, remarks, or triggering conditions and edit its alarm objects.

Directions

Setting an alarm policy

1. Log in to the TDSQL-C for MySQL console.
2. Select a region at the top and proceed according to the actually used view mode:
Tab view
List View
Click Target Cluster in the cluster list on the left to enter the cluster management page.
Find the target cluster in the cluster list and click the Cluster ID or Manage in the Operation column to enter the cluster management page.

3. Select Monitoring and Alarms on the cluster management page and click Configure Alarms on the right.


4. On the page displayed, select Manage Monitoring Policy > Create Policy.
5. On the policy creation page, configure the following parameters and click Complete.


Parameter
Description
Policy Name
Enter the policy name, which can contain up to 60 characters.
Remarks
Enter remarks for the policy, which can contain up to 100 characters.
Monitoring Type
Select Tencent Cloud services.
Policy Type
Select TencentDB >TDSQL-C > MySQL.
Alarm Object
Find the object instance to be associated with by selecting the region where the object is located or searching for the instance ID of the object.
Trigger Condition
Select a predefined template or manually configure the alarm trigger condition, which is a semantic condition composed of metric, comparison, threshold, statistical period, and duration. For example, if the metric is disk utilization, the comparison is >, the threshold is 80%, the statistical period is 5 minutes, and the duration is two statistical periods, then the data on disk utilization of a database will be collected once every five minutes, and an alarm will be triggered if the disk utilization exceeds 80% for two consecutive times.
Configure 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 Creating Notification Template.

Managing an alarm policy

1. In the alarm policy list, click the name of the target alarm policy to enter the alarm policy management page.
2. Select Policy Details on the alarm policy management page.


3. Select the configuration item to be modified as needed, such as policy name, remarks, trigger condition, and alarm object.

Help and Support

Was this page helpful?

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

Feedback