Data Transfer Service
- Release Notes and Announcements
- Announcements
- Product Introduction
- Specification Description
- Preparations
- Network Preparation
- Interworking Between local IDC and Tencent Cloud
- Adding DTS IP Addresses to the Allowlist of the Corresponding Databases
- DTS Service Permission Preparation
- Data Migration
- Migration to MySQL Series
- Migrating to MySQL
- Migrating to MariaDB
- Migrating to TDSQL-C for MySQL
- Migrating to TDSQL MySQL
- Migrating to TDSQL TDStore
- Advanced Operations for MySQL Series Migration
- Processing for MySQL Series Pre-Check Failure
- Migrating to PostgreSQL
- Processing for PostgreSQL Series Pre-Check Failure
- Migrating to MongoDB
- Migration from MongoDB to MongoDB
- Fix for Verification Failure
- MongoDB Data Consistency Verification
- Migrating to SQL Server
- Migration from SQL Server to TencentDB for SQL Server
- Pre-Validation Failure Handling
- Migrating to TencentDB for Redis
- Migration from Redis to Redis
- Fix for Verification Failure
- Migrating to KeeWiDB
- Migration from Redis to KeeWiDB
- Task Management
- Data Sync
- Sync to MySQL series
- Sync to MySQL
- Sync to MariaDB
- Sync to TDSQL-C for MySQL
- Sync to TDSQL for MySQL
- Sync from TDSQL for MySQL to TDSQL for MySQL
- Sync to TDSQL TDStore
- MySQL Series Advanced Sync Operations
- MySQL series Pre Validation Failed Processing
- Synchronize to PostgreSQL
- PostgreSQL Pre Validation does not Pass Processing
- Synchronize to Kafka
- MySQL/MariaDB/Percona/TDSQL-C MySQL Sync to Kafka
- TDSQL MySQL Sync to Kafka
- Task Management
- Data Subscription (Kafka Edition)
- MySQL series Data Subscription
- Consuming MySQL Data
- Advanced Subscription Operations
- Fix for Verification Failure
- Data Subscription for TDSQL PostgreSQL
- Fix for Verification Failure
- MongoDB Data Subscription
- Fix for Verification Failure
- Task Management
- Consumption Management
- Fix for Verification Failure
- Monitoring and Alarms
- Configuring Metric Alarms and Event Alarms via the Console
- Practical Tutorial
- FAQs
- Error Handling
- API Documentation
- Making API Requests
- (NewDTS) Data Migration APIs
- Data Sync APIs
- Data Consistency Check APIs
- (NewDTS) Data Subscription APIs
- DTS API 2018-03-30
- Data Subscription APIs
- Making API Requests
- DTS APIs
- Service Agreement
DocumentationData Transfer ServiceMonitoring and AlarmsConfiguring Metric Alarms and Event Alarms via the ConsoleConfiguring Alarm Policy for Data Subscription
Configuring Alarm Policy for Data Subscription
Last updated: 2024-07-08 15:56:51
Overview
You can use Tencent Cloud Observability Platform (TCOP) to set alarm rules for important metrics during data subscription. TCOP will send notifications to you as soon as a metric becomes abnormal, so you can take corresponding measures.
Metrics of both the data producer and consumer can be monitored. Data consumption has three monitoring dimensions: partition, group, and task.
This document describes how to set notification rules for metric alarms, including the trigger condition and scope of metric alarms, notification channels, notification period, and recipient groups.
Adding Alarm Policy
1. Log in to the TCOP console.
2. On the left sidebar, select Alarm Management > Policy Management to enter the alarm policy configuration page.
3. Click Create Policy and configure a alarm policy as detailed below:
Configuration Type | Configuration Item | Description |
Basic Info | Policy Name | Custom policy name |
| Remarks | Custom policy remarks |
| Monitoring Type | Select "Tencent Cloud services". |
| Policy Type | Select a policy type for the cloud service you want to monitor. Data migration: Metrics in data migration scenarios are monitored. Data sync: Metrics in data sync scenarios are monitored. Data subscription (Kafka edition): Producer metrics in data subscription (Kafka edition) in NewDTS are monitored. Data subscription (Kafka edition) – Consumption information: Consumer metrics in data subscription (Kafka edition) in NewDTS are monitored. If you select this option, you can further select the “Partition”, “Group”, or “Task” dimension. Data subscription: Metrics in data subscription in OldDTS are monitored. |
Configure Alarm Rule | Alarm Object | If you select "Instance ID", the alarm policy is associated with the selected instance. If you select "Instance Group", the alarm policy is associated with the selected instance group. If you select “All Objects”, the alarm policy is associated with all instances the current account has permission to access. If you have selected "Data subscription (Kafka edition) – Consumption information" as the policy type, here you can further select a consumer group and partition. |
| Configure manually – Metric Alarm | Alarm trigger condition: You can specify that the alarm is triggered when any or all metrics meet the set condition. Sample configuration: The metric is "Source Instance Data Extraction RPS", the statistical period is 1 minute, the comparison relation is "<", the threshold is "1", and the consecutive monitoring duration is "3 consecutive data points". Configuration effect: The "Source Instance Data Extraction RPS" metric data is collected once every minute. If the number of rows read by DTS from the source database per second is below 1 for three consecutive times, an alarm will be triggered. Alarm frequency: You can set a notification repetition rule so that the alarm notification is repeatedly sent at the specified frequency, such as once every hour, every 2 hours, and every 24 hours. |
| Configure manually – Event Alarm | Select the event for which the alarm is reported.
The configuration here can also be configured in EventBridge. If you have already configured the event alarm as instructed in Configuring Event Alarm, the configuration here is not necessary. |
| Select Template | Click Select Template and select a template in the drop-down list. For more information, see Configuring Trigger Condition Template. If a created template is not displayed, click the Refresh icon on the right to refresh the template list. |
Configure Alarm Notification | Notification Template | You can select a preset or custom notification template. Each alarm policy can be bound to three notification templates at most. |
4. After configuring the above information, click Save.
Modifying Alarm Policy
1. Log in to the TCOP console.
2. On the left sidebar, select Alarm Management > Policy Management, and click the ID of the policy you want to modify to enter the alarm policy management page.
3. Modify information such as the trigger condition, alarm object, and alarm notification as needed.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No