Centralize CLS Alert Notifications with Tencent Cloud Observability Platform
Reuse observability notification templates for log alerts, reduce duplicate channel maintenance, and review alert history in one place
Alert delivery becomes hard to operate when every product owns its own notification setup. Log alerts, cloud product alerts, application monitoring alerts, and frontend monitoring alerts may all need SMS, email, phone calls, WeChat, Enterprise WeChat, DingTalk, Feishu, Slack, PagerDuty, Teams, or a custom callback.
CLS can send alert notifications through Tencent Cloud Observability Platform notification templates. That lets log alerts reuse the same notification strategy used by other monitoring products.
A centralized alerting setup puts cloud product monitoring, application monitoring, frontend monitoring, and CLS log alerts behind the same Observability Platform notification strategy. The log alert policy still belongs to CLS, but the receiver configuration, escalation path, and alert-governance view are shared.
Why centralize alert notifications
| Operational issue | Centralized notification benefit |
|---|---|
| Repeated channel configuration | One notification template can be reused by CLS and other observability products. |
| Scattered alert delivery | Teams receive alerts through consistent channels and policies. |
| Missed escalation paths | Duty schedules, phone-call rotation, and SCF delivery can be attached through the Observability Platform. |
| Hard-to-review history | CLS alert history can be viewed in alert governance. |
Configure a CLS alert policy to use an Observability Platform template
- Open the CLS alert policy configuration.
- Set the notification method to the Observability Platform notification template.
- Select an existing template that was already created in Tencent Cloud Observability Platform.
- Create a new template when no suitable template exists.
- Save the alert policy.
- Review alert delivery and history in the Observability Platform alert-governance view.
The configuration path has three checkpoints:
| Checkpoint | What to verify |
|---|---|
| CLS alert policy | The notification method is set to an Observability Platform notification template rather than a standalone CLS-only receiver. |
| Notification template | An existing template is selected, or a new template is created with the required channels and escalation behavior. |
| Alert governance | CLS alert history appears in the Observability Platform governance view so operators can review alert status and delivery history in one place. |
Supported delivery patterns
This configuration supports a broad set of delivery channels: SMS, email, phone, WeChat, Enterprise WeChat, DingTalk, Feishu, Slack, PagerDuty, Teams, and custom webhook callbacks.
Advanced alerting features can also be used through the Observability Platform, including duty schedules, phone-call rotation, and delivery of alert messages to SCF. Alert convergence is described as a future supported capability in this capability set.
Operational checklist
- Create shared notification templates for common incident-response paths.
- Reuse templates from CLS alert policies instead of duplicating channel settings in each policy.
- Keep channel ownership clear: incident channels, escalation channels, and webhook callbacks should have different templates when their lifecycle differs.
- Review CLS alert history from the alert-governance view after enabling the template.
- Use advanced capabilities such as duty schedules or phone rotation for alerts that must not be missed.
FAQ
Can CLS alerts share the same notification policy as other cloud monitoring alerts?
Yes. CLS alert policies can use Tencent Cloud Observability Platform notification templates, allowing log alerts and other monitoring alerts to share notification strategies.
Which channels are available?
The available channels include SMS, email, phone, WeChat, Enterprise WeChat, DingTalk, Feishu, Slack, PagerDuty, Teams, and custom interface callbacks.
