Ensure the Alerting Mechanism Is Enabled and Configured

MediumLevel 1Manual reviewtdsql

Description

HA primary-replica switchover Critical An instance underwent a switchover Backup failure Major A data backup task failed Insufficient disk space Critical Data directory disk usage exceeded the threshold ZK connection anomaly Critical Metadata service connection interrupted VIP anomaly Critical Virtual IP switched or lost 3.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

In the TDSQL management platform confirm alert notification channels (email, SMS, WeCom, etc.) and recipients are configured, all Critical-level alert types (node/instance down, primary switch, replication delay, disk usage, backup failure) are enabled, and aggregation/escalation policies exist. Missing channels or disabled critical alerts are a finding.

How it is fixed

Fix method: Guidance or infrastructure patch

1. Configure alert recipients and channels. 2. Ensure all Critical-level alerts are enabled. 3. Configure alert aggregation and escalation policies.

Properties

Operating systems: Any
Tags: tdsqlmonitoring
Reference: CIS Tencent TDSQL 10.3.22 Benchmark v1.0.0 - 12.4 Ensure the Alerting Mechanism Is Enabled and Configured