tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary

Setting Event Alarms

PDF
Focus Mode
Font Size
Last updated: 2024-06-18 11:11:49
TencentDB for MySQL supports the event alarm feature. When you set an event pattern, event target, and recipient, if an exception event is detected, the event alarm will send alarm notifications to the recipient through various optional channels. This document explains how to set up event alarms.

Step 1: Enabling EventBridge

Tencent Cloud EventBridge implements permission management through Cloud Access Management (CAM). CAM is a permission and access management service provided by Tencent Cloud, mainly used to help customers securely manage access rights to resources under Tencent Cloud accounts. Users can create, manage, and terminate users (groups) with CAM, and control the access rights of other users to Tencent Cloud resources using identity and policy management. Before using EventBridge, you need to activate the service on the product page. For the method to activate with a main account and to authorize sub-accounts to use this service, see Activate EventBridge.

Step 2: Setting Event Alarms

Note:
For alarm events generated by TencentDB for MySQL, all will be delivered to the Tencent Cloud service event set, with this delivery being the default and not supporting modification or editing.
After enabling the Tencent Cloud EventBridge service, it will automatically create a default cloud service event set in the Guangzhou region. Alarm events generated by TencentDB for MySQL will be automatically delivered to it.

Method 1: Tencent Cloud EventBridge Configuration

2. Select Guangzhou as the region at the top.
3. Click on the default event set under the cloud service event set.

4. Click Manage Event Rules, then on the redirection page, click Create (taking creating an event rule as an example, if an event rule already exists, you can directly modify it with no need to recreate it).
5. After completing the following configuration on the new event rule page, click Next.
Parameter
Description
Rule name
Fill in the rule name, which can only include letters, digits, underscores (_), and hyphens (-), must start with a letter, end with a digit or letter, and contain 2-60 characters.
Rule description
Fill in the rule description, which can only include digits, Chinese and English characters and common punctuation marks, and must be no more than 200 characters.
Tag
Customize whether to enable tags. Once enabled, tags can be added to the event rule.
Data conversion
Event data conversion helps you easily process the event content. For example, you can extract and parse fields within the event, perform mapping reorganization, and then deliver it to the event target.
Event Example
Provides an example of event structure for reference in configuring event matching rules. You can find the target template under event example selection for reference, and select TencentDB for MySQL as the cloud service type.
Rule pattern
Supports form mode and custom events, where form mode is recommended for convenience.
Tencent Cloud service
Select TencentDB for MySQL.
Event Type
Select the alarm event type as needed.
Subject to match
Select the matching object for event alarms.
6. Complete relevant settings on the event target page, check Enable Event rules now, and click Complete. (There are various trigger methods available, which you can choose as needed. The following example selects "Message Push" as the trigger method. The channel push will be sent to the designated contacts. You need to set the recipient user separately at the recipient area. The notification period shall be agreed upon with the account user. The receiving channels can include Email, message center, SMS, and Telephone).
Note:
To configure multiple event targets, click Add.

7. After an event message push is set, if an event alarm set in the configuration occurs, the system will notify via the receiving channels set for your specified recipients.

Method 2: TCOP Alarm Policy Configuration

Create an Alarm Policy
1. Log in to the TCOP Console, select Alarm Management > Policy Management page from the left navigation.
2. On the alarm policy list page, click Create Policy.

3. On the policy creation page, complete the settings for basic information, alarm rules, and alarm notifications.
Policy Type: Divided into host monitoring and standby monitoring, with each applicable to different instance types.
Alarm Object: The object instance to be associated can be found by selecting the object's region or searching for the object's instance ID.
Trigger Condition: Find event alarms, click Add Event, and add alarm events according to business needs.

Configure Alarm Notification: Supports selection of system preset notification templates and user-defined notification templates. Each alarm policy can be bound to a maximum of three notification templates. For user-defined notification templates, see Create New Notification Template.
Select a system preset template.

Create a template.

4. After confirmation, click Complete.
Associate Alarm Objects
After creating an alarm policy, you can also associate it with other alarm objects (other instances that need this alarm policy). When objects meet the alarm trigger conditions, an alarm will be sent.
1. On the Alarm Policy List Page, click Alarm Policy Name to enter the Manage Alarm Policy page.
2. In the Alarm Object column of the Alarm Policy Management page, click Add Object.
3. In the pop-up dialog box, select the alarm object you wish to associate, and click OK to associate the alarm object.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback