tencent cloud

Data Transfer Service

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Data Migration
Data Sync
Data Subscription (Kafka Edition)
Strengths
Supported Regions
Specification Description
Purchase Guide
Billing Overview
Configuration Change Description
Payment Overdue
Refund
Getting Started
Data Migration Guide
Data Sync Guide
Data Subscription Guide (Kafka Edition)
Preparations
Business Evaluation
Network Preparation
Adding DTS IP Addresses to the Allowlist of the Corresponding Databases
DTS Service Permission Preparation
Database and Permission Preparation
Configuring Binlog in Self-Built MySQL
Data Migration
Databases Supported by Data Migration
Cross-Account TencentDB Instance Migration
Migration to MySQL Series
Migrating to PostgreSQL
Migrating to MongoDB
Migrating to SQL Server
Migrating to Tencent Cloud Distributed Cache
Task Management
Data Sync
Databases Supported by Data Sync
Cross-Account TencentDB Instance Sync
Sync to MySQL series
Synchronize to PostgreSQL
Synchronization to MongoDB
Synchronize to Kafka
Task Management
Data Subscription (Kafka Edition)
Databases Supported by Data Subscription
MySQL series Data Subscription
Data Subscription for TDSQL PostgreSQL
MongoDB Data Subscription
Task Management
Consumption Management
Fix for Verification Failure
Check Item Overview
Cutover Description
Monitoring and Alarms
Supported Monitoring Indicators
Supported Events
Configuring Metric Alarms and Event Alarms via the Console
Configuring Indicator Monitoring and Event Alarm by APIs
Ops Management
Configuring Maintenance Time
Task Status Change Description
Practical Tutorial
Synchronizing Local Database to the Cloud
Creating Two-Way Sync Data Structure
Creating Many-to-One Sync Data Structure
Creating Multi-Site Active-Active IDC Architecture
Selecting Data Sync Conflict Resolution Policy
Using CLB as Proxy for Cross-Account Database Migration
Migrating Self-Built Databases to Tencent Cloud Databases via CCN
Best Practices for DTS Performance Tuning
FAQs
Data Migration
Data Sync
FAQs for Data Subscription Kafka Edition
Regular Expressions for Subscription
Error Handling
Common Errors
Failed Connectivity Test
Failed or Alarmed Check Item
Inability to Select Subnet During CCN Access
Slow or Stuck Migration
Data Sync Delay
High Data Subscription Delay
Data Consumption Exception
API Documentation
History
Introduction
API Category
Making API Requests
(NewDTS) Data Migration APIs
Data Sync APIs
Data Consistency Check APIs
(NewDTS) Data Subscription APIs
Data Types
Error Codes
DTS API 2018-03-30
Service Agreement
Service Level Agreements

Configuring Alarm Policy for Data Sync

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-07-08 15:56:51

Overview

You can use Tencent Cloud Observability Platform (TCOP) to set alarm rules for important metrics during data sync. TCOP will send notifications to you as soon as a metric becomes abnormal, so you can take corresponding measures.
This document describes how to set notification rules for metric alarms, including the trigger condition and scope of metric alarms, form of notifications, time period for notifications, and recipient group.

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. In this scenario, select Data Transfer Service/Data sync.
Data migration: Metrics in data migration scenarios are monitored.
Data sync: Metrics in data sync scenarios are monitored.
Data subscription (Kafka edition): 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.
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.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック