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

PagerDuty Integration

Synchronize via webhook
Flashduty implements PagerDuty Events API with full input and response compatibility. This allows you to push alert events to Flashduty using the PagerDuty protocol for automated alert noise reduction.
Similarly, for alert systems that already support pushing events to PagerDuty (such as ElastAlert), you only need to modify the destination push URL to utilize the PagerDuty protocol for pushing events to Flashduty.

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 alert events 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 PagerDuty 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 event's payload information.
Expand
1.
Go to the Flashduty console, select Integration Center=>Alert Events to enter the integration selection page
2.
Select PagerDuty 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 PagerDuty#


Request URL#

{api_host}/event/push/alert/pagerduty
This URL supports both PagerDuty V1 and V2 Events API. You must modify the PagerDuty URL to this address.

PagerDuty V2 Events#

Reference Documentation:#

PagerDuty V2 Events

Authentication Methods:#

Choose one of these two methods:
Method 1: Include integration_key parameter in QueryString
Method 2: Pass integration_key as routing_key parameter in Payload

PagerDuty V1 Events#

Reference Documentation:#

PagerDuty V1 Events

Authentication Methods:#

Choose one of these two methods:
Method 1: Include integration_key parameter in QueryString
Method 2: Pass integration_key as service_key parameter in Payload

Configuration Example#

Using ElastAlert2 as an example:
1.
Step 1: Obtain Push URL
Enter integration name on the current page and save. Reopen integration details and copy the push URL, such as:
{api_host}/event/push/alert/pagerduty?integration_key=xxx
2.
Step 2: Modify Push URL
Modify the corresponding source code of your deployed ElastAlert instance, view diff:
drawing
3.
Step 3: Report Alert Events
Follow the ElastAlert PagerDuty push configuration documentation steps to configure alerts:
name: "b"
type: "frequency"
index: "pgy_audit*"
is_enabled: true
num_events: 1
realert:
  minutes: 1
terms_size: 50
scan_entire_timeframe: true
timeframe:
  minutes: 60
timestamp_field: "created_at"
timestamp_type: "unix_ms"
use_strftime_index: false
alert_subject: "Test {0} 123 aa☃ {1}"
alert_subject_args:
  - "account_id"
  - "operation"
alert_text: "Test {0}  123 bb☃ {1}"
alert_text_args:
  - "request_id"
  - "operation_name"
filter:
  - query:
      query_string:
        query: "created_at:*"

# ------- FlashDuty ----------------
alert: pagerduty
pagerduty_service_key: xxx
pagerduty_client_name: wahaha
pagerduty_api_version: v2
pagerduty_v2_payload_class: ping failure
pagerduty_v2_payload_component: mysql
pagerduty_v2_payload_group: app-stack
pagerduty_v2_payload_severity: error
pagerduty_v2_payload_source: mysql.host.name
# ------- FlashDuty ----------------
4.
Step 4: Restart ElastAlert and wait for alerts to trigger
上一页
Open Falcon Integration
下一页
Tencent BlueKing Integration
Built with