Skip to main content
Use the Webhook integration of an Airbrake project to send error notifications to Flashduty On-call. Each Airbrake error maps to one Flashduty alert, and repeated notifications for the same error merge into that alert. Airbrake’s webhook sends no “resolved” notification, so alerts are closed by the channel’s auto-close or manually.

In Flashduty On-call

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

Use a dedicated integration

  1. In the Flashduty console, select Channel and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add integration
  3. Select Airbrake, then click Save
  4. Open the generated integration card and copy the Push URL

Use a shared integration

  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select Airbrake and enter an integration name
  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

Configure Airbrake

1

Add a Webhook integration

Open the Airbrake project you want to connect, go to the project’s Integrations settings, and select Webhook. Airbrake’s documentation does not give the menu path to this page, so follow what the Airbrake console shows.Click Save. Airbrake posts when a new error occurs or a resolved error occurs again.
2

Turn on auto-close

Where: Flashduty › Channels › Configuration › Settings › Advanced settingsAirbrake’s webhook only sends error notifications and has no recovery event: when an error is marked resolved in Airbrake, Flashduty is not notified.Turn on auto-close in the channel that receives these alerts, with a suggested duration of 24 hours. A repeated notification for the same error within the grouping window updates the same alert; after the alert is closed, the next notification opens a new one.
3

Verify

Trigger a new error in an application that reports to Airbrake. A few seconds later, the integration in Flashduty shows a Latest event time and an active alert appears. Its title is the error message, and the error_id label matches the error’s ID in Airbrake.Airbrake’s documentation does not describe a test notification body, so Flashduty does not treat test deliveries specially. If a test delivery arrives, handle it as an ordinary alert and close it manually.

Alert key

Flashduty computes the Alert Key from error.id (the Airbrake error ID) in the webhook body. Every notification for the same error uses the same Alert Key, and changes to the error message, occurrence count, environment, or last occurrence time do not change it. A notification without error.id is rejected.

Status and severity

The Airbrake webhook carries no severity. Every notification is a Warning trigger.

Labels

Troubleshooting

  • Flashduty returns an invalid-parameter error: confirm the URL is complete and includes integration_key
  • Alerts do not recover: Airbrake sends no recovery notification; turn on the channel’s auto-close or close alerts manually
  • No notifications arrive: check whether the production-only option is on and whether the error’s environment is production
For field details, see Airbrake Webhook.