Alarm Upgrade

Last updated: 2021-08-10 17:37:51

Background

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.
Note:

Alarm Policy Transfer

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.
    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 MariaDB in Policy Type, query alarm policies in this category, and download the previously configured alarm policies of the legacy MariaDB policy type.
  2. Configure new alarm policies.
    1. On the Alarm Policy page, click Create.
    2. 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.
  3. 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.
  4. 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 TypeMetric/Event AlarmLegacy Metric/Event Alarm NameNew Policy TypeNew Metric/Event Alarm Name
MariaDB Metric alarmCPU utilization Cloud Database - MariaDB - InstanceCPU utilization
Metric alarmPrimary-Replica switch Cloud Database - MariaDB - InstancePrimary-Replica switches
Metric alarm Available disk space Cloud Database - MariaDB - InstanceAvailable data disk space
Metric alarm Log disk space Cloud Database - MariaDB - InstanceMinimum remaining binlog disk space
Metric alarm SELECT queries Cloud Database - MariaDB - InstanceTotal SELECT requests
Metric alarm Slow queries Cloud Database - MariaDB - InstanceSlow queries
Metric alarm UPDATE queries Cloud Database - MariaDB - InstanceUPDATE requests
Metric alarm INSERT queries Cloud Database - MariaDB - InstanceINSERT requests
Metric alarm DELETE queries Cloud Database - MariaDB - InstanceDELETE requests
Metric alarm Available memory size Cloud Database - MariaDB - InstanceAvailable cache space
Metric alarm Disk IOPS Cloud Database - MariaDB - InstanceIO utilization
Metric alarm Active connections Cloud Database - MariaDB - InstanceTotal active threads
Metric alarm Connection utilization Cloud Database - MariaDB - InstanceMaximum database connection utilization
Metric alarm Disk utilization Cloud Database - MariaDB - InstanceData disk utilization
Metric alarm REPLACE_SELECT queries Cloud Database - MariaDB - InstanceREPLACE_SELECT requests
Metric alarm Logical reads from InnoDB disk Cloud Database - MariaDB - InstanceTotal logical reads from InnoDB disk
Metric alarm Logical reads from InnoDB buffer pool Cloud Database - MariaDB - InstanceTotal logical reads from InnoDB buffer pool
Metric alarm Pages read into InnoDB buffer pool by read-ahead thread Cloud Database - MariaDB - InstanceTotal pages read into InnoDB buffer pool by read-ahead thread
Metric alarm Rows deleted from InnoDB tables Cloud Database - MariaDB - InstanceRows deleted from InnoDB Tables
Metric alarm Rows inserted into InnoDB tables Cloud Database - MariaDB - InstanceRows inserted into InnoDB tables
Metric alarm Rows updated to InnoDB tables Cloud Database - MariaDB - InstanceRows updated to InnoDB tables
Metric alarm Used log disk space Cloud Database - MariaDB - InstanceUsed binlog disk space

New Metric Description

Policy TypeMetric/Event AlarmMetric/Event Alarm Name
Cloud Database - MariaDB Metric alarm Total rows read from InnoDB tables
Metric alarm Minimum replica node delay
Metric alarmBuffer cache hit ratio
Metric alarm REPLACE count
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 SQL throughput
Metric alarm SQL error throughput
Metric alarm SQL success throughput
Metric alarm Total client connections
Metric alarm Total requests of primary and replica nodes
Metric alarm Total open connections
Metric alarm Total maximum connections