Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. Integrations
  2. 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
  1. Integrations
  2. Alerts integration

ElastAlert2 Alert Integration

Push ElastAlert2 alerts to Flashduty via webhook, to achieve automatic alert noise reduction.

In Flashduty#

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

Using Dedicated Integration#

Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
Expand
1.
Go to the Flashduty console, select Channel, and enter a channel's details page
2.
Select the Integration tab, click Add Integration to enter the integration page
3.
Choose ElastAlert 2 integration and click Save to generate a card
4.
Click the generated card to view the Integration Key, copy it for later use, and you're done

Using Shared Integration#

Choose this method when you need to route alerts to different channels based on the alert event's payload information.
Expand
1.
Go to the Flashduty console, select Integration Center=>Alert Events to enter the integration selection page
2.
Select ElastAlert 2 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 Integration Key for later use
5.
Done

In ElastAlert 2#

Configure ElastAlert 2 Alerts#

Follow the ElastAlert PagerDuty push configuration document
1.
Create or edit the alert rule file, for example rules/elastalert2_alert.yaml.
2.
Fill in the flashduty alert type in the alert field.
3.
Fill in the integrated integration key in the flashduty_integration_key field.
4.
The flashduty_title and flashduty_event_status are required fields, and other fields can be filled in as needed. For the field definitions, please refer to the following table.
FieldRequiredTypeDefinition
title是stringThe alert title, it cannot exceed 512 characters.
event_status是stringThe alert status.

Enum values (capitalized): Critical：severe, Warning：warning, Info：reminder, Ok：recovery.

When specified as Ok, it means automatic recovery of the alert.
alert_key否stringThe alert identifier, used to update or automatically recover existing alerts. You can customize this value, but it cannot exceed 255 characters. You can also rely on the system to automatically generate this value, which will be returned in the response. If you report a recovery event, this value must exist.
description否stringThe alert description
check否stringThe alert check item
resource否stringThe alert resource
service否stringThe alert service name
metric否stringThe alert metric name
group否stringThe alert group
cluster否stringThe alert cluster
app否stringThe alert application
env否stringThe alert environment
5.
Restart ElastAlert and wait for the alert to trigger.
修改于 2025-03-27 07:56:41
上一页
Keep Integration
下一页
StateCloud Alert Events
Built with