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
DocumentationTDSQL-C for MySQLOperation GuideMonitoring and AlarmsAlarmsEvent AlarmSupported Event Types

Supported Event Types

PDF
Focus Mode
Font Size
Last updated: 2025-11-20 16:15:43
This document describes the event types in TDSQL-C for MySQL for which alarms can be reported.
Note:
To ensure that event names are clear and easy to understand, starting from February 27, 2024, the event indicator name " HA " in TDSQL-C for MySQL will be optimized to " Unplanned High Availability Switch ", and " Fault Avoidance " will be optimized to " Planned High Availability Switch ". Thank you for your understanding and support.
Event
Event Name
Event Description
TencentCloud API operation event (CloudAudit)
Cloud API actions (CloudAudit)
User operation invoking TencentCloud API
Unplanned high availability switch
HA
Instance experienced unplanned high availability switch
Console operation event (CloudAudit)
Console operations (CloudAudit)
User operation using the console
Database agent exception
Database agent exception
Database agent exception
Mini program operation event (CloudAudit)
Mini program operations (CloudAudit)
User operations with mini program
Memory OOM
OOM
System memory overload
Instance read-only (excessive storage)
Instance read-only due to storage full
Storage space capacity exceeds the limit, write operations are blocked, and the read-only mode is enabled
Version upgrade event
Version upgrade events
Cluster executing minor version upgrade
Cross-AZ latency
Cross-AZ latency
High primary-replica latency of cross-availability zones
Note：
For cross-AZ delay events, the conditions for sending alarms are as follows:
An alarm will be sent if the delayed data exceeds 2 GB and persists for more than 2 hours.
An alarm will be sent if the cross-AZ primary-secondary latency exceeds 3,600 seconds and persists for more than 2 hours.
After such an event occurs, it is recommended that you check the cluster status to reduce cross-AZ replica node latency.
Database agent mount node removal
The database agent mount node is removed
Database agent mount node removal due to failure
RDMA degradation
RdmaDowngrade
Instance RDMA degradation
Planned high availability switch
FailureAvoid
Ops behavior initiated based on the need to avoid failures and risks
Database audit low risk
AuditLowRisk
Audit risk level
Medium risk for database audit
AuditMediumRisk
Audit risk level
Database audit high risk
AuditHighRisk
Audit risk level
Cluster isolation
ClusterIsolated
The cluster enters the isolation status
Cross-server migration of Serverless instances is successful.
ServerlessExpandNodeBySwitchSuccess
Execution of cross-server migration of Serverless instances is successful
Recovery of storage usage exceeding the limit
StopStorageOver
The storage space recovers to the status before exceeding the limit
Storage usage exceeding the limit
ReportStorageOver
The storage space usage exceeds the limit
Previous Topic: OverviewNext Topic: Setting Event Alarms

Help and Support

Was this page helpful?

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

Feedback