Unify Tencent Cloud CLS Alert Notifications with Observability Templates

Log alerts rarely live alone. In real operations, log monitoring, cloud product monitoring, application monitoring, and endpoint monitoring often need to notify the same teams. If every product maintains its own recipients, channels, rotations, and callbacks, alert operations become duplicated and easy to miss.

The source article introduces a new CLS capability: Tencent Cloud Cloud Log Service alerts can now send notifications through Tencent Cloud Observability Platform notification templates. The practical change is simple but useful: CLS alert policies can reuse the same notification policy layer as cloud product monitoring, APM, and terminal performance monitoring.

Why unify alert notification templates?

The original article frames the problem as alert fragmentation. Separate notification settings across products can create three operational issues:

Problem	What happens in practice	What the new path changes
Repeated maintenance	Teams configure recipients and channels in several products	CLS can reuse Observability Platform templates
Scattered alerts	Log alerts and cloud-resource alerts are reviewed in different places	Notification strategy becomes more consistent across products
Missed escalation	A channel or rotation may be updated in one product but not another	Duty schedules, phone rotation, and callbacks can be managed centrally

Capability map from the source article

The source article highlights three capabilities.

Capability	Source-backed detail
Unified configuration	CLS alert policies can directly reuse Observability Platform notification templates. The same notification strategy can be shared with cloud product monitoring, APM, and endpoint performance monitoring alerts.
Multi-channel notification	Supported channels include SMS, email, phone calls, WeChat, Enterprise WeChat, DingTalk, Feishu, Slack, PagerDuty, Teams, and custom callback APIs.
Advanced alert handling	The Observability Platform can provide duty schedules, phone notification rotation, and alert-message delivery to SCF. The source also mentions future support for alert convergence.

Configure CLS to use an Observability Platform template

The usage flow is short:

1. In a CLS alert policy, choose Observability Platform notification template as the notification method.
2. Select an existing notification template that was already created in the Tencent Cloud Observability Platform.
3. If no suitable template exists, create a new template.
4. After alerts are delivered, review CLS alert history through Alert Governance in the Observability Platform.

The screenshot above shows the CLS alert-policy configuration page. The highlighted area is the notification method. Instead of configuring a standalone CLS-only receiver, the policy uses the Observability Platform template type.

This screenshot shows the template-selection step. In English, the operator is choosing a previously created notification template from the Observability Platform and applying it to the CLS alert policy.

If the existing list does not contain the right template, the dialog allows the operator to create one. The practical translation of this step is: define the receiver policy once, then attach it to CLS alerts.

The final screenshot shows the Observability Platform's Alert Governance area. The source article says CLS alert history can be reviewed there, which gives operators one place to trace notification events after alerts fire.

When this is the right pattern

Use this integration when:

• log alerts and cloud-resource alerts should notify the same team;
• a team already manages duty schedules or notification rotations in the Observability Platform;
• CLS alerts need channels such as Enterprise WeChat, Slack, PagerDuty, Teams, or custom callbacks;
• operations teams want alert history and governance to be reviewed in a central alert console.

Keep standalone CLS notification settings only when a log alert has an intentionally isolated audience or an independent callback path.

Operational checklist

• Create or identify the Observability Platform notification template first.
• In the CLS alert policy, set the notification method to the Observability Platform template option.
• Select the existing template or create a new one from the policy configuration flow.
• Test that the expected channel receives the alert.
• Use Alert Governance to review historical CLS alert events after delivery.

FAQ

What problem does this solve for CLS alerting?

It reduces duplicated notification configuration and makes CLS alert delivery part of the same alert-management layer used by other Tencent Cloud observability products.

Which notification channels are supported by the source article?

The source lists SMS, email, phone calls, WeChat, Enterprise WeChat, DingTalk, Feishu, Slack, PagerDuty, Teams, and custom callback APIs.

Does this replace alert rules?

No. The source article describes notification delivery and governance. CLS still owns the log alert policy and alert condition; the Observability Platform template owns the notification route.