• Products
  • Get started
  • Documentation
  • Resources

Integrate Opsgenie with Airbrake

Airbrake logo

What does Opsgenie offer Airbrake users?

Use Opsgenie’s Airbrake Integration to forward Airbrake incidents to Opsgenie. Opsgenie determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls, iOS & Android push notifications, and escalates alerts until the alert is acknowledged or closed.

Functionality of the integration

When an error (incident) is captured in Airbrake, an alert is created in Opsgenie.

Add Airbrake Integration in Opsgenie

  1. Go to Opsgenie’s Airbrake Integration page.

Under the Free and Essentials plans, the tabs under the Team dashboard are limited to Main, Integrations, Members, and Activity Stream.

2. Specify who is notified of Airbrake alerts using the Teams field. Autocomplete suggestions are provided as you type.

An alternative for Step 1) and Step 2) is to add the integration from the Team Dashboard of the team which will own the integration. To add an integration directly to a team, navigate to the Team Dashboard and open Integrations tab. Click Add Integration and select the integration that you would like to add.

3. Copy the integration URL which includes Opsgenie endpoint as well as the API key.

4. Click Save Integration.

Airbrake integration

Configuration in Airbrake

  1. In Airbrake, go to "Integrations" from your project's page.

  2. Select Webhook.

  3. Populate the webhook URL field with the integration URL copied previously while saving the integration.

  4. Click Save.

  5. Alert properties are configured from Airbrake Integration / Advanced Settings page.

  6. ​All set! Now manage your Airbrake alerts at Opsgenie and leverage its full alerting functionality.

Airbrake alert properties

Sample Webhook Message from Opsgenie Airbrake

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 { "error": { "id": 37463546, "error_message": "RuntimeError: You threw an exception for testing", "error_class": "RuntimeError", "file": "[PROJECT_ROOT]/app/controllers/pages_controller.rb", "line_number": 35, "project": { "id": 1055, "name": "AirbrakeProject" }, "last_notice": { "id": 4505303522, "request_method": "metot", "request_url": "http://airbrake.io:445/pages/exception_test", "backtrace": [ "[PROJECT_ROOT]/app/controllers/pages_controller.rb:35:in `exception_tester'", "[PROJECT_ROOT]/app/middleware/conditional_heroku_nav.rb:19:in `_call'", "[PROJECT_ROOT]/app/middleware/conditional_heroku_nav.rb:11:in `call_without_newrelic'" ] }, "environment": "production", "first_occurred_at": "2012-02-23T22:03:03Z", "last_occurred_at": "2012-03-21T08:37:15Z", "times_occurred": 118 } }

This payload is parsed by Opsgenie as:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 { "error_id": 37463546, "error_message": "RuntimeError: You threw an exception for testing", "file": "[PROJECT_ROOT]/app/controllers/pages_controller.rb", "line_number": 35, "project_id": 1055, "project_name": "AirbrakeProject", "environment": "production", "first_occurred_at": "2012-02-23T22:03:03Z", "last_occurred_at": "2012-03-21T08:37:15Z", "times_occurred": 118, "last_notice_request_method": "metot", "last_notice_request_url": "http://airbrake.io:445/pages/exception_test", "last_notice_backtrace": [ "[PROJECT_ROOT]/app/controllers/pages_controller.rb:35:in `exception_tester'", "[PROJECT_ROOT]/app/middleware/conditional_heroku_nav.rb:19:in `_call'", "[PROJECT_ROOT]/app/middleware/conditional_heroku_nav.rb:11:in `call_without_newrelic'" ] }

Sample alert

Airbrake sample alert

 

Last modified on Dec 23, 2020
Cached at 8:55 PM on May 8, 2021 |

Additional Help

Ask the Community