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

Configure Event Alarm Push

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

Overview

DTS can use EventBridge to configure alarms for ‍abnormal task interruption events. EventBridge will send notifications to recipients as soon as an event is triggered so that they can take timely measures.
After EventBridge is activated, it will automatically create a default Tencent Cloud service event bus in Guangzhou region, to which alarm events generated by DTS will be automatically published.
This document describes how to set notification rules for event alarms, that is, filter alarmed tasks and set the ‍alarm publishing method, alarm notification method, and recipient group.

Prerequisite

You have activated the EventBridge service. For more information, see Activating EventBridge.

Directions

Viewing the event list

1. Log in to the EventBridge console.
2. Click Event Bus on the left sidebar. The default event bus is stored in the Guangzhou region. You don't need to switch the region.
Note
You will be asked to authorize EventBridge when you log in to the EventBridge console for the first time. For directions, see Activating EventBridge. If you have already authorized it, skip this step.
3. Click the Event bus ID and go to Basic information > Event Source > Cloud Monitor to view the DTS monitoring event.

Configuring event alarm rules

1. Log in to the EventBridge console and select Event Rule on the left sidebar.
2. On the Event Rule page, select a region and event bus and click Create. The default event bus is stored in the Guangzhou region. You don't need to switch the region.
3. On the Basic information page, enter the rule name and description. In the Event matching module below, you can select Template or Custom Event for the Mode field as needed.
If you select Template, you need to configure the Tencent Cloud service and Event Type fields. You can select all events or specific event types for Event Type.
If you select Custom Event, see the syntaxes in different scenarios as described in Sample Syntax for Custom Event Alarms.
4. After configuring the Rule pattern page, click Next.
5. On the Create event rule > Delivery Target page, set the following parameters and click Complete.
Parameter
Description
Trigger method
Here, select Notification message.
Message template
General notification template is selected by default. If you select Monitoring alert template, see instructions in Creating Notification Template.
Alarm content
Chinese is selected by default. You can select other options based on your needs.
Notification method
You can select either or both of the following two notification methods: API callback and publishing channel.
publishing channel: If you select this option, you need to further select the recipients, notification period, and receiving channel.
You can configure the sub-accounts under your Tencent Cloud account as the recipients. To add more recipients or recipient groups, go to the CAM console to add them first, then you can select them here.
Add
To configure different trigger methods, click Add at the bottom to add more delivery targets.
Enable event rules now
If you select this option, the event rule will immediately take effect after you click Complete.
6. Return to the event rule list to confirm that the created event rule has been enabled. If any task exception triggers an alarm subsequently, the recipients can receive the notifications.

Sample Syntax for Custom Event Alarms

Below are the sample syntaxes in different scenarios:
Receive alarms of all DTS events. The following syntax represents that alarms can be pushed for all DTS ‍alarm events according to the event rule.
{
"source":"dts.cloud.tencent"
}
Receive event alarms of DTS migration, sync, and subscription tasks. The three fields under the type of the following syntax represent the migration, sync, and subscription task interruption events respectively. If you don't need to receive alarms of any of these events, delete the corresponding syntax content.
{
  "source":"dts.cloud.tencent",
  "type":[
    "dts:ErrorEvent:MigratejobInterruption",
    "dts:ErrorEvent:ReplicationInterruption",
    "dts:ErrorEvent:SubscriptionInterruption"
  ]
}
Receive event alarms of a single DTS task. The following syntax represents that alarms can only be pushed for the alarm event generated by the specified task (ID: sync-jt12XXgt). Those triggered by other events will be discarded and cannot be pushed to recipients.
{
"source":"dts.cloud.tencent",
"subject":"sync-jt12XXgt"
}
Receive event alarms of multiple DTS tasks.
{
"source":"dts.cloud.tencent",
"subject":["sync-jt12XXgt","dts-a5uqXXhs"]
}
Receive event alarms of DTS migration tasks in the specified region. Here, region refers to the target instance region.
{
  "source":"dts.cloud.tencent",
  "type":"dts:ErrorEvent:MigratejobInterruption",
  "region":"ap-guangzhou"
}
For more information about the matching rules, see Event Pattern.


ヘルプとサポート

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

フィードバック