Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. Alerts integration
  • Getting Started
    • Introduction
    • Quick start
    • FAQ
    • Product Comparison
  • Incidents
    • What is an Incident
    • View Incidents
    • Handle Incidents
    • Escalations and Assignments
    • Custom Fields
    • Custom Actions
    • Alert Noise Reduction
    • Past Incidents
    • Outlier Incidents
  • Configure Flashduty
    • Channels
    • Integrate Alerts
    • Alert Noise Reduction
    • Escalation Rules
    • Label Enrichment
    • Schedules
    • Templates
    • Service Calendars
    • Preferences
    • Alert Routing
    • Silence and Inhibition
    • Filters
    • Notification Bots
    • Alert Pipeline
  • Platform
    • Teams and Members
    • Permissions
    • Single Sign-On
    • Insights
  • Advanced Features
    • Referencing Variables
    • Dynamic Assignment
  • Integrations
    • Alerts integration
      • Standard Alert Integration
      • Email Integration
      • Nightingale/FlashCat Integration
      • Prometheus Integration
      • Grafana Integration
      • Zabbix Integration
      • Uptime Kuma Integration
      • Alibaba Cloud ARMS Integration
      • Alibaba Cloud Monitor CM Event Integration
      • Alibaba Cloud Monitor CM Metrics Integration
      • Alibaba Cloud SLS Integration
      • AWS CloudWatch Integration
      • Azure Monitor Integration
      • Baidu Cloud BCM Integration
      • Huawei Cloud CES Integration
      • Influxdata Integration
      • Open Falcon Integration
      • PagerDuty Integration
      • Tencent BlueKing Integration
      • Tencent Cloud CLS Integration
      • Tencent Cloud Monitor CM Integration
      • Tencent Cloud EventBridge
      • OceanBase Integration
      • Graylog Integration
      • Skywalking Integration
      • Sentry Integration
      • Jiankongbao Integration
      • AWS EventBridge Integration
      • Dynatrace Integration
      • Huawei Cloud LTS Integration
      • GCP Integration
      • Splunk Alert Events Integration
      • AppDynamics Alert Integration
      • SolarWinds Alert Events Integration
      • Volcengine CM Alert Events Integration
      • Volcengine CM Event Center Integration
      • Volcengine TLS Integration
      • OpManager Integration
      • Meraki Integration
      • Keep Integration
      • ElastAlert2 Alert Integration
      • StateCloud Alert Events
      • Guance Alert Events
      • Zilliz Alert Events
      • Huawei Cloud APM Alerts
      • zstack integration
    • Change integration
      • Standard Change Event
      • Jira Issue Events
    • IM integration
      • Feishu (Lark) Integration Guide
      • Dingtalk Integration
      • WeCom Integration
      • Slack Integration
      • Microsoft Teams Integration
    • Single Sign-On
      • Authing Integration
      • Keycloak Guide
      • OpenLDAP Guide
    • Webhooks
      • Alert webhook
      • Incident webhook
      • Costom action
  • Terms
    • Terms of Service
    • User Agreement/Privary Policy
    • SLA
    • Data Security
  1. Alerts integration

Tencent Cloud CLS Integration

Sync Tencent Cloud Log Service (CLS) monitoring alerts to Flashduty via webhook for automated alert noise reduction.

In Flashduty#


You can obtain an integration push URL through either of these two methods:

Using Private Integration#

Choose this simpler option when you don't need to route alerts to different channels.
Expand
1.
Go to the Flashduty console, select channel, and enter a specific channel's details page
2.
Select the Integrations tab, click Add Integration to enter the integration page
3.
Choose Tencent Cloud CLS integration and click Save to generate a card
4.
Click the generated card to view the push URL, copy it for later use, and you're done

Using Shared Integration#

Choose this option when you need to route alerts to different channels based on the alert payload information.
Expand
1.
Go to the Flashduty console, select Integration Center=>Alerts to enter the integration selection page
2.
Select Tencent Cloud CLS integration:
Integration Name: Define a name for this integration
3.
Configure the default route and select the corresponding channel (after the integration is created, you can go to Route to configure more routing rules)
4.
Click Save and copy the newly generated push URL for later use
5.
Done

In Tencent Cloud CLS#


Step 1: Configure Notification Channel Group
1.
Log in to your Tencent Cloud Console, select CLS service, and go to Monitoring Alerts - Notification Channel Groups
2.
Click Create to start
drawing
3.
As shown, enter a specific channel group name in Name, select "Custom API Callback" for Channel Type, fill in the integration push URL in Callback URL, and select POST for Request Method
4.
Click OK to save, Add to add multiple channels
Step 2: Configure Alert Policy
1.
Log in to your Tencent Cloud Console, select CLS service, and go to Monitoring Alerts - Alert Policies
2.
Click Create to start
drawing
3.
As shown, enter a specific alert name in Alert Name, select the specific log topic
4.
Fill in specific query statements in Execution Statement, select time range for query period, click Preview to check execution results, enter specific trigger conditions
5.
For Alert Level, choose between Critical, Warning, and Info based on alert severity, select execution cycle as needed
6.
Multi-dimensional Analysis allows additional log analysis when alerts trigger, attaching results to notifications to help identify alert causes. This analysis doesn't affect alert trigger conditions.
7.
For alert notifications, Notification Channel Group can be linked to specific channel groups
Step 3: Configure Custom Callback
1.
After linking the channel group, you can see callback content configuration
2.
Request headers can be added as needed
3.
Request content format reference:
{
    "uin": "{{escape .UIN}}",
    "nickname": "{{escape .Nickname}}",
    "region": "{{escape .Region}}",
    "alarm": "{{escape .Alarm}}",
    "alarm_id": "{{escape .AlarmID}}",
    "condition": "{{escape .Condition}}",
    "happen_threshold": "{{escape .HappenThreshold}}",
    "alert_threshold": "{{escape .AlertThreshold}}",
    "topic": "{{escape .Topic}}",
    "topic_id": "{{escape .TopicId}}",
    "level": "{{escape .Level}}",
    "label": {{.Label}},
    "start_time": "{{escape .StartTime}}",
    "start_time_unix": "{{escape .StartTimeUnix}}",
    "notify_time": "{{escape .NotifyTime}}",
    "notify_time_unix": "{{escape .NotifyTimeUnix}}",
    "notify_type": "{{escape .NotifyType}}",
    "consecutive_alert_nums": "{{escape .ConsecutiveAlertNums}}",
    "duration": "{{escape .Duration}}",
    "trigger_params": "{{escape .TriggerParams}}",
    "record_group_id": "{{escape .RecordGroupId}}",
    "detail_url": "{{escape .DetailUrl}}",
    "query_url": "{{escape .QueryUrl}}",
    "message": {{.Message}},
    "query_result": {{.QueryResult}},
    "query_log": {{.QueryLog}},
    "analysis_result": {{.AnalysisResult}}
}

Status Mapping#


Tencent Cloud CLS monitoring alert level mapping to Flashduty:
Tencent Cloud CLSFlashdutyStatus
InfoInfoInfo
WarnWarningWarning
CriticalCriticalCritical
修改于 2025-03-27 07:50:42
上一页
Tencent BlueKing Integration
下一页
Tencent Cloud Monitor CM Integration
Built with