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

Creating Notification Template

PDF
Focus Mode
Font Size
Last updated: 2026-02-11 18:04:40
This document describes how to create a notification template in the Tencent Cloud Observability Platform alarm module.

Use Cases

One template can be quickly reused for multiple policies, eliminating the need to repeatedly configure user notifications.
User notification methods can be configured in a more personalized way. For example, you can configure the alarm receiving channel as SMS/email by day and phone by night.
Different user groups take effect in different notification periods. For example, group A receives alarms by day, while group B by night.
Different groups can receive different types of alarms. For example, group A receives notifications of alarm triggering, while group B alarm resolving.

Prerequisites

View notification templates: the sub-account must have the read permission of Tencent Cloud Observability Platform.
Create and edit notification templates: the sub-account must have the write permission of Tencent Cloud Observability Platform.
Note:
For more information on how to grant sub-accounts permissions, please see Cloud Access Management (CAM).

Use Limits

Feature
Limit
User notification
Up to five items can be added
API callback
Up to three URLs accessible over the public network can be entered

Directions

Creating notification template

1. Enter the Alarm Management > Alarm Configuration > Notification Template page in the Tencent Cloud Observability Platform Console.
2. Click Create Notification Template and enter relevant information in "Create Notification Template".
Template Name: enter a custom template name.
Notification Type:
Alarm Trigger: a notification will be sent when an alarm is triggered.
Alarm Recovery: a notification will be sent when an alarm is resolved.
User Notification:
Recipient Object: you can choose a recipient group or recipient. If you need to create a group, please see Creating Alarm Recipient Group.
Notification Period: define the time period for receiving alarms.
Receiving Channel: three alarm channels are supported: email, SMS, and phone. You can also set different channels and notification periods in different user dimensions. For more information, please see Alarm Type, Channel, and Quota. Description of phone alarm settings:
Polling Times: the maximum number of dials for each polled recipient when there is no valid reach.
Polling Sequence: alarm calls will be dialed according to the order of the recipients. You can adjust the order of calling by dragging up and down recipients.
Polling Interval: time interval at which alarm calls will be dialed according to the order of the recipients.
Reach Notification: notifications will be to all recipients after successful reception of the call or calling all recipients. SMS messages are counted against the quota.
API Callback: you can enter up to three URLs accessible over the public network as the callback API addresses, and Tencent Cloud Observability Platform will push alarm messages to them promptly. If the HTTP response returns code 200, the verification is successful. For more information on alarm callback fields, please see Alarm Callback Parameters.


Note:
After you save the callback URL, the system will automatically verify your URL once. The timeout threshold for this verification is 5 seconds. When an alarm policy created by the user is triggered or the alarm is resolved, the alarm messages will be pushed through the API callbacks. An alarm message can be pushed up to three times, and the timeout threshold for each request is 5 seconds.
When an alarm policy created by the user is triggered or the alarm is resolved, the alarm messages will be pushed through the API callbacks. API callbacks also support repeated alarms.
The outbound IP of the Tencent Cloud Observability Platform callback API is dynamically and randomly allocated, so no specific IP information can be provided to you, but the IP port is fixed at 80. We recommend you configure a weighted opening policy in the security group based on port 80.

Default notification template

The system automatically creates a default notification template for you as detailed below:
Feature
Default Configuration
Template name
Preset notification template
Notification type
Alarm trigger, alarm recovery
Alarm recipient
Root account admin
Notification period
00:00:00–23:59:59 (all day)
Receiving channel
Email, SMS

Help and Support

Was this page helpful?

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

Feedback