Get started with Opsgenie as an admin
Start building your teams, integrate your tools and create on-call schedules.
Integrate Opsgenie with Airbrake
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
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 Responders field. Autocomplete suggestions are provided as you type.
Did you know that you can also add this integration from your team dashboard?
If you want your team to be the owner of this integration, add it from your team dashboard. Opsgenie will assign the alerts received through this integration to your team only.
To do that;
Go to Teams,
Find your team and select it to go to your team dashboard,
From your team navigation, select Integrations,
Select Add integration.
3. Copy the integration URL which includes Opsgenie endpoint as well as the API key.
4. Click Save Integration.
Configuration in Airbrake
In Airbrake, go to "Integrations" from your project's page.
Select Webhook.
Populate the webhook URL field with the integration URL copied previously while saving the integration.
Click Save.
Alert properties are configured from Airbrake Integration / Advanced Settings page.
All set! Now manage your Airbrake alerts at Opsgenie and leverage its full alerting functionality.
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
Last modified on Jun 18, 2021
Cached at 7:01 AM on Sep 20, 2021 |
Was this helpful?