TencentDB for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Database Architecture
- Database Instance
- Kernel Features
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Parallel Query
- Security Features
- Stability Features
- Purchase Guide
- Getting Started
- Connecting to MySQL Instance
- Database Audit
- Audit Rule Template
- MySQL Cluster Edition
- Maintenance Management Instance
- Operation Guide
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Database Proxy Kernel Features
- Database Proxy Management
- Automatic Read/Write Separation Feature
- Connection Pool Feature
- Other Features
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Restoring Database from Backup File
- Monitoring and Alarms
- Operation Logs
- Practical Tutorial
- Calling MySQL APIs in Python
- White Paper
- Performance White Paper
- Performance Test Report
- Troubleshooting
- Connections
- API Documentation
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- Database Proxy APIs
- Database Audit APIs
- Security APIs
- Account APIs
- Backup APIs
- Database APIs
- Monitoring APIs
- Log-related API
- FAQs
- Backup
- Connection and Login
- Instance Upgrade
- Performance and Memory
- Service Agreement
- Reference
DocumentationTencentDB for MySQLRelease Notes and AnnouncementsAnnouncementsMonitoring Module Upgrade
Monitoring Module Upgrade
Last updated: 2023-08-09 18:18:03
To provide you with more stable and high-quality TencentDB for MySQL service and reduce the delay in monitoring data collection, we will upgrade and optimize its monitoring feature.
Change Time
01:00–06:00 AM Beijing time (GMT+8) from 2022-03-25 (Friday) to 2022-04-15 (Friday).
Detailed Schedule
2022-03-25 (Friday): Singapore, Frankfurt, and Virginia
2022-03-28 (Monday): Silicon Valley, Toronto, São Paulo, and Jakarta
2022-03-29 (Tuesday): Mumbai, Bangkok, Seoul, Tokyo, Hong Kong (China), and Taipei (China)
2022-03-30 (Wednesday): Chengdu and Chongqing
2022-04-01 (Friday): Shenzhen, Hangzhou, Nanjing, and Tianjin
2022-04-04 (Monday): Beijing (Zones 5, 6, and 7)
2022-04-05 (Tuesday): Beijing (Zones 3 and 4)
2022-04-06 (Wednesday): Beijing (Zones 1 and 2)
2022-04-07 (Thursday): Guangzhou (Zones 6 and 7)
2022-04-08 (Friday): Guangzhou (Zones 4 and 5)
2022-04-11 (Monday): Guangzhou (Zones 2 and 3)
2022-04-12 (Tuesday): Guangzhou (Zone 1)
2022-04-13 (Wednesday): Shanghai (Zones 4 and 5)
2022-04-14 (Thursday) Shanghai (Zone 2)
2022-04-15 (Friday): Shanghai (Zones 1 and 3)
Impact of Change
There will be one or two breakpoints in certain monitoring metrics, but they will have no effect on the operation of your database instances. Key metrics such as CPU, memory utilization, and read/write rate will not be affected, nor will alarm events such as HA switch and running failures.
We apologize for any inconvenience caused.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No