Alarm Upgrade

Last updated: 2021-08-12 11:00:35

    Background

    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:

    Alarm Policy Migration

    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. Configure new alarm policies.
      1. On the Alarm Policy page, click Create.
      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 TypeMetric/Event AlarmLegacy Metric/Event Alarm NameNew Policy TypeNew Metric/Event Alarm Name
    Tencent Distributed SQL Metric alarmCPU utilization Cloud Database - TDSQL MySQL - InstanceMaximum CPU utilization of source node
    Metric alarmStorage space utilization Cloud Database - TDSQL MySQL - InstanceMaximum data disk utilization of source node
    Metric alarmSlow queries Cloud Database - TDSQL MySQL - InstanceTotal slow queries of source nodes
    Metric alarmActive connections Cloud Database - TDSQL MySQL - InstanceTotal active threads
    Metric alarmCache hit rate Cloud Database - TDSQL MySQL - InstanceMinimum cache hit rate of source node
    Metric alarmDatabase connections Cloud Database - TDSQL MySQL - InstanceTotal client connections
    Metric alarmReplica lag Cloud Database - TDSQL MySQL - InstanceSecondary node delay
    Metric alarmPrimary-Secondary switch Cloud Database - TDSQL MySQL - InstancePrimary-Secondary switches

    New Metric Description

    Policy TypeMetric/Event AlarmMetric/Event Alarm Name
    Cloud Database - TDSQL MySQL Metric alarmCPU utilization
    Metric alarmTotal UPDATE requests of source nodes
    Metric alarmTotal open connections
    Metric alarmTotal maximum connections
    Metric alarmSQL Throughput
    Metric alarmSQL Error Throughput
    Metric alarmSQL Success Throughput
    Metric alarmRequests consuming less than 5 ms
    Metric alarmRequests consuming 5–20 ms
    Metric alarmRequests consuming 21–30 ms
    Metric alarmRequests consuming more than 30 ms
    Metric alarmMinimum remaining binlog disk space in all shards
    Metric alarmTotal binlog disk space of source nodes
    Metric alarmMaximum database connection utilization
    Metric alarmTotal available data disk space of source nodes
    Metric alarmTotal DELETE requests of source nodes
    Metric alarmMaximum IO utilization of source node
    Metric alarmTotal logical reads from InnoDB disk
    Metric alarmTotal pages read into InnoDB buffer pool by read-ahead thread
    Metric alarmTotal logical reads from InnoDB buffer pool
    Metric alarmTotal rows deleted from InnoDB tables on source nodes
    Metric alarmTotal rows inserted to InnoDB tables on source nodes
    Metric alarmTotal rows read from InnoDB tables
    Metric alarmTotal rows updated in InnoDB tables on source nodes
    Metric alarmTotal INSERT requests of source nodes
    Metric alarmTotal available cache of source nodes
    Metric alarmTotal REPLACE_SELECT requests of source nodes
    Metric alarmTotal REPLACE requests of source nodes
    Metric alarmTotal requests of source and replica nodes
    Metric alarmTotal SELECT requests