Skip to main content
Use the Webhook notification channel of a Rollbar project to send error items to Flashduty On-call. Each Rollbar item maps to one Flashduty alert: new, repeated, and reactivated occurrences trigger or update that alert, and the alert recovers when the item is marked resolved.

​
In Flashduty On-call

You can obtain an 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 an integration
  3. Select Rollbar, then click Save
  4. Open the generated integration card and copy the Push URL

​
Use a shared integration

  1. In the Flashduty console, select Integration Center → Alert Events
  2. Select Rollbar and enter an integration name
  3. Configure the default route and select a channel; after creation, add more rules under Route if needed
  4. Click Save and copy the generated Push URL

​
Configure Rollbar

Webhooks are configured per project. You need permission to change the project’s notification settings in Rollbar.
1

Enable the webhook channel

  1. Open the Rollbar project you want to connect and go to Settings → Notifications → Webhook
  2. Paste the complete Flashduty integration Push URL into URL. The URL must include integration_key
  3. Click Save. The channel is enabled when the URL is saved
2

Add notification rules

When the URL is saved for the first time, Rollbar creates a default rule set: New item, Item reactivated, Item reopened, 10^nth occurrence, Item resolved, and Deploy. Check the Rules list at the bottom of the page and use Add rule only for the rules that are missing, such as High occurrence rate. Do not add the same trigger twice, or each event is sent twice.We recommend enabling these rules:The default rules only send items at level error or higher (condition level >= error). To receive warning or info items, edit the rule and lower the level condition. Rules can also filter by environment and other conditions, so only items that need on-call attention are sent. Every occurrence (occurrence) sends one request per error occurrence. These requests also merge into the item’s alert, but the volume is high, so we do not recommend enabling it.
Keep the Item resolved rule enabled. Without it, Flashduty alerts do not recover when the item is resolved. Keep the rule’s payload format at the default JSON; Flashduty does not accept XML.
3

Verify the lifecycle

Raise a new error in an application that uses a Rollbar SDK and confirm that Flashduty receives an active alert. Then mark the item Resolved in Rollbar and confirm that the alert recovers.Send Test Notification on the Webhook settings page only checks that the URL is reachable: Flashduty returns success but does not create an alert. Deploy events are also accepted without creating an alert.

​
Alert Key

Flashduty uses the item id (data.item.id in the webhook) as the Alert Key. In Rollbar’s official webhook examples, the new_item, item_velocity, exp_repeat_item, and resolved_item events for the same item carry the same id. It is also the ID that the Rollbar API uses to look up an item. The number in an item URL (such as .../items/40) is the project-level counter and is kept only as a label. Changes to the title, level, environment, or occurrence count do not change the Alert Key. Item events without data.item.id are rejected.

​
Status and severity

The event name sets the alert status: resolved_item recovers the alert, and every other item event triggers it. The item level (data.item.level) sets the severity: New Rollbar items default to error. To be notified at Critical for a class of errors, change the item level to critical in Rollbar or set the level in your SDK.

​
Labels

​
Troubleshooting

  • Rollbar shows failed deliveries: Confirm that the URL is complete and includes integration_key, and check each attempt under the rule’s History. Rollbar retries failed deliveries and automatically disables rules that keep failing; re-enable the rule on the Webhook settings page after fixing the cause
  • Flashduty returns a parameter error: Confirm that the rule’s payload format is JSON
  • The alert does not recover: Confirm that the Item resolved rule exists. Muting an item in Rollbar does not send a webhook, so close the corresponding alert in Flashduty manually
  • The test succeeds but real errors do not arrive: Check whether the rule’s filters (environment, level, and so on) match the error
For field details, see Rollbar Webhooks and Item Levels.