tencent cloud

Tencent Cloud Observability Platform

Release Notes and Announcements
Release Notes
Product Introduction
Overview
Strengths
Basic Features
Basic Concepts
Use Cases
Use Limits
Purchase Guide
Tencent Cloud Product Monitoring
Application Performance Management
Mobile App Performance Monitoring
Real User Monitoring
Cloud Automated Testing
Prometheus Monitoring
Grafana
EventBridge
PTS
Quick Start
Monitoring Overview
Instance Group
Tencent Cloud Product Monitoring
Application Performance Management
Real User Monitoring
Cloud Automated Testing
Performance Testing Service
Prometheus Getting Started
Grafana
Dashboard Creation
EventBridge
Alarm Service
Cloud Product Monitoring
Tencent Cloud Service Metrics
Operation Guide
CVM Agents
Cloud Product Monitoring Integration with Grafana
Troubleshooting
Practical Tutorial
Application Performance Management
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Parameter Information
FAQs
Mobile App Performance Monitoring
Overview
Operation Guide
Access Guide
Practical Tutorial
Tencent Cloud Real User Monitoring
Product Introduction
Operation Guide
Connection Guide
FAQs
Cloud Automated Testing
Product Introduction
Operation Guide
FAQs
Performance Testing Service
Overview
Operation Guide
Practice Tutorial
JavaScript API List
FAQs
Prometheus Monitoring
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Terraform
FAQs
Grafana
Product Introduction
Operation Guide
Guide on Grafana Common Features
FAQs
Dashboard
Overview
Operation Guide
Alarm Management
Console Operation Guide
Troubleshooting
FAQs
EventBridge
Product Introduction
Operation Guide
Practical Tutorial
FAQs
Report Management
FAQs
General
Alarm Service
Concepts
Monitoring Charts
CVM Agents
Dynamic Alarm Threshold
CM Connection to Grafana
Documentation Guide
Related Agreements
Application Performance Management Service Level Agreement
APM Privacy Policy
APM Data Processing And Security Agreement
RUM Service Level Agreement
Mobile Performance Monitoring Service Level Agreement
Cloud Automated Testing Service Level Agreement
Prometheus Service Level Agreement
TCMG Service Level Agreements
PTS Service Level Agreement
PTS Use Limits
Cloud Monitor Service Level Agreement
API Documentation
History
Introduction
API Category
Making API Requests
Monitoring Data Query APIs
Alarm APIs
Legacy Alert APIs
Notification Template APIs
TMP APIs
Grafana Service APIs
Event Center APIs
TencentCloud Managed Service for Prometheus APIs
Monitoring APIs
Data Types
Error Codes
Glossary

Message Push Target

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-11-01 21:01:01

Overview

For Tencent Cloud service events collected by the default Tencent Cloud service event bus, EventBridge allows you to configure message push to push Cloud Monitor events to user terminals in real time.
Note
Currently, message push can only be bound to the default Tencent Cloud service event bus.
By default, the number of events delivered to a target cannot exceed 2,000 per day.




Directions

1. Log in to the EventBridge console and click Event rule in the left sidebar. Select the default Tencent Cloud service event bus.
2. On the Event rule page, click Create event rule, as shown below:

3. On the Create event rule page, select Notification message for Trigger Method and set other parameters such as the recipient and delivery method as prompted, as shown below:



Note
Use limits: For SMS message delivery, a notification message can contain up to 500 characters. For phone delivery, a notification message can contain up to 350 characters. If fields such as the instance name are too long, notification messages may fail to be sent due to excessive length. We recommend that you configure multiple delivery channels.
Cross-MLC-border API callback may fail due to network instability.

Message Push Template

Tencent Cloud ${Service name abbreviation} Alert
Dear Tencent Cloud user,

An alert is triggered for Tencent Cloud ${4} under your account (Account ID: ${Account ID}; Name: ${Account name}). Check and resolve the issue in time.



Alerted event: ${Event details}
Alerted service: ${Service name abbreviation}
Alerted resource: ${Resource ID}
Alarm region: ${Resource region}
Event generation time: ${Alarm time}
Event status: ${Recovered/Not recovered/Stateless}

For more details, log in to the EventBridge console.

Callback Samples

Note
DDoS event callbacks are different from others.

Sample callback of a monitoring alarm template

{
"sessionId": "xxxxxxxxxxxxxxxx", // Event ID
"alarmStatus": "1",//Event.Status
"alarmType": "event",// The value is fixed, indicating an event alarm
"alarmObjInfo": {
"region": "sh", // Event region
"dimensions": { // Additional description of the resource, which is subjected to the related Tencent Cloud service (CVM here)
"unInstanceId": "ins-xxxxx",
"objDetail": {
"deviceLanIp": "xxxx",
"deviceWanIp": ""
"uniqVpcId": "vpc-xxx"
},
"deviceName": "xxx"
}
},
"alarmPolicyInfo": { // Alarm policy information, which is compatible with existing callbacks of Tencent Cloud Observability Platform.
"policyName": "xxxx", // EventBridge event rule name
"conditions": {
"productName": "cvm", // Abbreviation of the related Tencent Cloud service
"eventName": "guest_reboot", // Event type
"alarmNotifyType": "", // It is left empty and is compatible with existing callbacks of Tencent Cloud Observability Platform.
"alarmNotifyPeriod": "" // It is left empty and is compatible with existing callbacks of Tencent Cloud Observability Platform.
}
},
"additionalMsg": [{ // Additional information of the event, which is determined by the event reporter (CVM here)
"key": "alias",
"value": "xxxx"
}, {
"key": "deviceLanIp",
"value": "xxxx"
}, {
"key": "deviceWanIp",
"value": ""
}, {
"key": "uniqVpcId",
"value": ""
}],
"firstOccurTime": "2021-10-19 11:15:47", // Alerted time
"durationTime": 0, // Duration
"recoverTime": "0" // Recovery time
}

Sample callback of a general notification template

{
"id":"xxxxxxxxxxxxxxxx", // Event ID.
"type":"cdb:ErrorEvent:PlannedSwitch", // Event type. Example: cdb.
"specversion":"1.0",
"source":"cdb.cloud.tencent", // The Tencent Cloud service.
"subject":"xxxxxx", // Event resource, such as the instance ID.
"time":1662538320000, // Timestamp when the event occurred, which is accurate to milliseconds.
"region":"ap-beijing", // Event region.
"datacontenttype":"application/json;charset=utf-8",
"status":"0", // Event status. Valid values: `0`: recovered. `1`: triggered. `-`: stateless.
"tags":"",
"data":{
"additionalMsg":[ // Additional information of the event. The information varies with the Tencent Cloud services.
{
"key":"InstanceName",
"value":"xxxxx"
},
{
"key":"IP",
"value":"xxxxxxx"
}
],
"dimensions":[ // Additional information of the event resource. The information varies with the Tencent Cloud services.
{
"key":"InstanceId",
"value":"cdb-xxxxxx"
}
]
}
}

DDoS callback sample

{
"id":"xxxxxxxxxxxxxxxx",
"type":"antiddos:ErrorEvent:DDoSAlaram",
"specversion":"1.0",
"source":"antiddos.cloud.tencent",
"subject":"xx.xx.xx.xx",
"time":1662538320000,
"region":"ap-beijing",
"datacontenttype":"application/json;charset=utf-8",
"status":"0",
"tags":null,
"data":{
"Appid":xxxxxxxxx,
"InstanceId":"ins-xxx",
"Ip":"xx.xx.xx.xx",
"NickName":" xxxxx",
"Region":"ap-beijing",
"Uin":"xxxxxxxxxxx"
}
}


ヘルプとサポート

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

フィードバック