Skip to main content
Flashduty implements PagerDuty Events API with full input and response compatibility. This allows you to push alert events to Flashduty using the PagerDuty protocol. 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 On-call

You can get the integration push URL in either of the following ways.

Use a dedicated integration

Choose this option if all alerts go to one channel. It’s the simpler setup.
  1. In the Flashduty console, select Channel and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add integration
  3. Choose PagerDuty Compatible integration and click Save to generate a card
  4. Open the generated integration card and copy the Push URL

Use a shared integration

Choose this option if you need to route alerts to different channels based on the alert payload.
  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select PagerDuty Compatible integration:
    • Integration Name: Define a name for this integration
  3. Configure the default route and select a channel. You can add more rules under Routing after creation
  4. Click Save and copy the generated Push URL

In your alerting system

Request URL

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

Status and severity

Any other V2 severity value is rejected. A non-trigger event must carry dedup_key (incident_key in V1), otherwise the request is rejected.

Configuration example

Using ElastAlert2 as an example:
1

Change the push URL in ElastAlert2

Where: ElastAlert2 source › elastalert/alerters/pagerduty.pyEnter an integration name on the current page and save, reopen the integration details and copy the push URL. Modify the corresponding source code of your deployed ElastAlert instance: replace both PagerDuty URLs (V2 and V1, https://events.pagerduty.com/v2/enqueue and https://events.pagerduty.com/generic/2010-04-15/create_event.json) in that file with:
View diff:drawing
2

Configure the alert in an ElastAlert2 rule file

Where: ElastAlert2 rule file › alertFollow the ElastAlert PagerDuty push configuration documentation to configure alerts. The settings that point to Flashduty:A complete rule example:
3

Restart ElastAlert and verify

Where: Terminal on the ElastAlert2 hostRestart ElastAlert and wait for the rule to trigger (pagerduty_event_type defaults to trigger). ElastAlert has no test button for Flashduty, so verify with a real alert that fires.