TencentDB for MariaDB 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 MariaDB type in the Cloud Monitor console.
The legacy MariaDB policy type was deactivated on July 29, 2021. You cannot configure new alarm policies in this type any more, and your previously configured MariaDB 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
MariaDB
22 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 - MariaDB
37 metrics
This policy type was released on April 1, 2021 with ongoing maintenance available.
After the legacy MariaDB policy type is deactivated, the system will automatically transfer previously configured alarm policies to the new MariaDB 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.
2. Log in to the Cloud Monitor console, select Alarm Configuration > Alarm Policy on the left sidebar, and click Advanced Filter.
3. On the pop-up page, select the alarm policy type corresponding to MariaDB in Policy Type, query alarm policies in this category, and download the previously configured alarm policies of the legacy MariaDB policy type.
4. Configure new alarm policies.
5. On the Alarm Policy page, click Create.
6. On the Create Alarm Policy page, select MariaDB for Policy Type and configure alarms according to the policies downloaded in step 1. For the configuration method, please see Creating Alarm Policy.
7. Verify whether the MariaDB 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.
8. After the new policy type is verified, delete the alarm policies previously configured under the legacy MariaDB policy type.
On the Alarm Policy page, filter alarm policies by the "MariaDB" 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
MariaDB
Metric alarm
CPU utilization
Cloud Database - MariaDB - Instance
CPU utilization
Metric alarm
Primary-Replica switch
Cloud Database - MariaDB - Instance
Primary-Replica switches
Metric alarm
Available disk space
Cloud Database - MariaDB - Instance
Available data disk space
Metric alarm
Log disk space
Cloud Database - MariaDB - Instance
Minimum remaining binlog disk space
Metric alarm
SELECT queries
Cloud Database - MariaDB - Instance
Total SELECT requests
Metric alarm
Slow queries
Cloud Database - MariaDB - Instance
Slow queries
Metric alarm
UPDATE queries
Cloud Database - MariaDB - Instance
UPDATE requests
Metric alarm
INSERT queries
Cloud Database - MariaDB - Instance
INSERT requests
Metric alarm
DELETE queries
Cloud Database - MariaDB - Instance
DELETE requests
Metric alarm
Available memory size
Cloud Database - MariaDB - Instance
Available cache space
Metric alarm
Disk IOPS
Cloud Database - MariaDB - Instance
IO utilization
Metric alarm
Active connections
Cloud Database - MariaDB - Instance
Total active threads
Metric alarm
Connection utilization
Cloud Database - MariaDB - Instance
Maximum database connection utilization
Metric alarm
Disk utilization
Cloud Database - MariaDB - Instance
Data disk utilization
Metric alarm
REPLACE_SELECT queries
Cloud Database - MariaDB - Instance
REPLACE_SELECT requests
Metric alarm
Logical reads from InnoDB disk
Cloud Database - MariaDB - Instance
Total logical reads from InnoDB disk
Metric alarm
Logical reads from InnoDB buffer pool
Cloud Database - MariaDB - Instance
Total logical reads from InnoDB buffer pool
Metric alarm
Pages read into InnoDB buffer pool by read-ahead thread
Cloud Database - MariaDB - Instance
Total pages read into InnoDB buffer pool by read-ahead thread
Yes
No
Was this page helpful?