TDSQL for MySQL upgraded the monitoring items for server and component services on April 1, 2021 by replacing the legacy alarm policy type and modifying hundreds of monitoring and alarm metrics. You can configure alarm policies of the TDSQL for MySQL type in the Cloud Monitor console.
The legacy TDSQL policy type was deactivated on July 29, 2021. You cannot configure new alarm policies in this type any more, and your previously configured TDSQL alarm polices will be gradually transferred to the new policy type.
Comparison of the legacy and new alarm policy types:
Policy Type
Metric Coverage
Support and Maintenance
Tencent Distributed SQL
8 metrics
This policy type was deactivated on July 29, 2021 and cannot be configured subsequently. All legacy alarm policies will be transferred to the new policy type.
Cloud Database - TDSQL MySQL - Instance
37 metrics
This policy type was released on April 1, 2021 with ongoing maintenance available.
Note:
The new TDSQL for MySQL policy type has covered all metrics of the legacy TDSQL policy type. For more information, please see Comparison Table of New and Legacy Metrics.
After the legacy TDSQL policy type is deactivated, the system will automatically transfer previously configured alarm policies to the new TDSQL for MySQL policy type on the backend.
Note:
Alarms may not be automatically transferred to the new alarm policy type by the system for certain instances or users. If this is the case for you, we will notify you through Message Center, email, or SMS. Then, please follow the manual transfer steps below to manually transfer the alarms.
Manual transfer steps
1. Sort out exiting alarm metrics and policies.
1. Log in to the Cloud Monitor console, select Alarm Configuration > Alarm Policy on the left sidebar, and click Advanced Filter.
2. On the pop-up page, select the alarm policy type corresponding to Tencent Distributed SQL in Policy Type, query alarm policies in this category, and download the previously configured alarm policies of the original Tencent Distributed SQL policy type.
2. On the Create Alarm Policy page, select Cloud Database - TDSQL MySQL - Instance for Policy Type and configure alarms according to the policies downloaded in step 1. For the alarm configuration method, please see Creating Alarm Policy.
3. Verify whether the TDSQL for MySQL alarm policies are enabled and can successfully trigger alarms.
Set a minimum trigger threshold in Metric alarm on the Create Alarm Policy page, choose to set a recipient or recipient group, and select the notification channel (email or SMS) to test a policy. For example, you can configure an alarm policy for the CPU utilization metric that triggers an alarm once per minute when the threshold is greater than or equal to 1% for one statistical period of one minute.
4. After the new policy type is verified, delete the alarm policies previously configured under the original TDSQL (legacy) policy type.
On the Alarm Policy page, filter alarm policies by the "Tencent Distributed SQL" policy type and delete the filtered policies according to the policy list downloaded in step 1.
If you encounter any issues during the transfer, please submit a ticket for assistance.
Comparison Table of New and Legacy Metrics
Legacy Policy Type
Metric/Event Alarm
Legacy Metric/Event Alarm Name
New Policy Type
New Metric/Event Alarm Name
Tencent Distributed SQL
Metric alarm
CPU utilization
Cloud Database - TDSQL MySQL - Instance
Maximum CPU utilization of source node
Metric alarm
Storage space utilization
Cloud Database - TDSQL MySQL - Instance
Maximum data disk utilization of source node
Metric alarm
Slow queries
Cloud Database - TDSQL MySQL - Instance
Total slow queries of source nodes
Metric alarm
Active connections
Cloud Database - TDSQL MySQL - Instance
Total active threads
Metric alarm
Cache hit rate
Cloud Database - TDSQL MySQL - Instance
Minimum cache hit rate of source node
Metric alarm
Database connections
Cloud Database - TDSQL MySQL - Instance
Total client connections
Metric alarm
Replica lag
Cloud Database - TDSQL MySQL - Instance
Secondary node delay
Metric alarm
Primary-Secondary switch
Cloud Database - TDSQL MySQL - Instance
Primary-Secondary switches
New Metric Description
Policy Type
Metric/Event Alarm
Metric/Event Alarm Name
Cloud Database - TDSQL MySQL
Metric alarm
CPU utilization
Metric alarm
Total UPDATE requests of source nodes
Metric alarm
Total open connections
Metric alarm
Total maximum connections
Metric alarm
SQL Throughput
Metric alarm
SQL Error Throughput
Metric alarm
SQL Success Throughput
Metric alarm
Requests consuming less than 5 ms
Metric alarm
Requests consuming 5–20 ms
Metric alarm
Requests consuming 21–30 ms
Metric alarm
Requests consuming more than 30 ms
Metric alarm
Minimum remaining binlog disk space in all shards
Metric alarm
Total binlog disk space of source nodes
Metric alarm
Maximum database connection utilization
Metric alarm
Total available data disk space of source nodes
Metric alarm
Total DELETE requests of source nodes
Metric alarm
Maximum IO utilization of source node
Metric alarm
Total logical reads from InnoDB disk
Metric alarm
Total pages read into InnoDB buffer pool by read-ahead thread
Metric alarm
Total logical reads from InnoDB buffer pool
Metric alarm
Total rows deleted from InnoDB tables on source nodes
Metric alarm
Total rows inserted to InnoDB tables on source nodes
Metric alarm
Total rows read from InnoDB tables
Metric alarm
Total rows updated in InnoDB tables on source nodes
Yes
No
Was this page helpful?