Skip to main content
Use the Webhook integration of a Honeybadger project to send error (fault), uptime check, and check-in events to Flashduty On-call. Each error, uptime check, and check-in maps to one Flashduty alert: an error triggers the alert when it occurs and recovers it when it is marked resolved; a site triggers the alert when it goes down and recovers it when it comes back up; a check-in triggers the alert when it is missing and recovers it when it reports again.

​
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 Honeybadger, 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 Honeybadger 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 Honeybadger

The Webhook integration is configured per project and is available only on Honeybadger’s Team, Business, and Enterprise plans. You need administrative privileges on the project.
1

Add a Webhook integration in Honeybadger

Where: Honeybadger › your project › Settings › Alerts & Integrations › Webhook
2

Choose the events to send

Where: Honeybadger › your project › Settings › Alerts & Integrations › WebhookIn the integration’s event options, select the events on-call should handle. Select both the trigger and the recovery option for each kind of event, otherwise alerts do not recover automatically. The error resolved and unresolved options are off by default and must be selected manually:Assigned (assigned), commented (commented) and deployed (deployed) events do not create alerts; Flashduty returns success and drops them. The environment filter, error filter and throttle settings in the options reduce the events pushed to Flashduty.
3

Save and verify

Where: Honeybadger › your project › Settings › Alerts & Integrations › Webhook
  1. Click save
  2. Trigger a new error in an application that uses the Honeybadger SDK and confirm Flashduty receives an active alert
  3. Mark the error Resolved in Honeybadger and confirm the original alert recovers
The Test this integration button on the integration settings page pushes an occurred event for a sample error of class TestingException. Flashduty creates a normal Warning alert for it, which you should close by hand afterwards.

​
Alert key

Flashduty builds the Alert Key from the object the event is about, so the trigger and recovery events of the same object share one Alert Key: The Alert Key combines the object type with the ID in the table, so an up event for a site does not recover that site’s certificate alert, and an error ID never merges with an equal project ID. Changes to the error message, environment, occurrence count, site name, and similar fields do not change the Alert Key. Events without the required ID are rejected.

​
Status and severity

Honeybadger events carry no severity, so Flashduty sets the status and severity from the event name: cert_will_expire and volume_spike have no recovery event. Close these alerts manually in Flashduty after handling them.

​
Labels

​
Troubleshooting

  • Webhook is not in the integration list: Confirm that the account is on the Team plan or higher and that you are a project administrator
  • Flashduty returns a parameter error: Confirm that the URL is complete and includes integration_key
  • The alert does not recover: Confirm that the matching recovery event is selected (error resolved, site back up, or check-in reporting again)
  • The test succeeds but real events do not arrive: Check the integration’s environment filters, error filters, and throttling, and whether the site is selected for uptime events
For field details, see Honeybadger Webhook.