• Products
  • Get started
  • Documentation
  • Resources

Integrate with Honeybadger

This article highlights a new alerting feature that's natively available in Jira Service Management which is gradually rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.

Honeybadger logo

What does the integration offer?

Integrate Jira Service Management with Honeybadger to dispatch the alerts generated by Honeybadger, determines the right people to notify based on on-call schedules– notifies via emails, SMS, phone calls, and iOS, and Android push notifications, and escalates alerts until they are acknowledged or closed.

How does the integration work?

  • When an alert is created in Honeybadger, an alert is also created in Jira Service Management automatically through the integration.

  • When an alert is closed in Honeybadger, the related alert is closed in Jira Service Management.

Set up the integration

Honeybadger is an API integration. Setting it up involves the following steps:

  • Add a Honeybadger integration in Jira Service Management

  • Configure the integration in Honeybadger

Add a Honeybadger integration

Bidirectional integrations aren’t supported in Free and Standard plans. All the other integrations are supported at a team level in Free and Standard; however, for their outgoing part to work, you need to upgrade to a higher plan. To add any integration at a site level through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be either on Premium or Enterprise.

Adding an integration from your team’s operations page makes your team the owner of the integration. This means Jira Service Management only assigns the alerts received through this integration to your team.

To add a Honeybadger integration in Jira Service Management, complete the following steps:

  1. Go to your team’s operations page.

  2. On the left navigation panel, select Integrations and then Add integration.

  3. Run a search and select “Honeybadger”.

  4. On the next screen, enter a name for the integration.

  5. Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.

  6. Select Continue.
    The integration is saved at this point.

  7. Expand the Steps to configure the integration section and copy the API key.
    You will use this key while configuring the integration in Honeybadger later.

  8. Select Turn on integration.
    The rules you create for the integration will work only if you turn on the integration.

Configure the integration in Honeybadger

To configure the integration of Honeybadger with Jira Service Management, complete the following steps:

  1. In your project In Honeybadger, go to Settings > Alerts & Integrations.

  2. Select Jira Service Management from the list of services.

  3. Depending on the instance you’re using, select US or EU for Endpoint.

  4. Paste the API key copied previously into Api key.

  5. Select Save Changes.

Honeybadger Events

When the Honeybadger Integration is added to Jira Service Management, two rules for creating alerts and two rules for closing alerts are automatically added for you which matches Honeybadger's fault and site based alerts. The content for those two types of alerts are totally different so use and modify those rules to stay up-to-date with all the features Honeybadger provides.

The following is the complete list of event types that Honeybadger generate and you can use for the Event field for filtering:

  • occurred

  • rate_exceeded

  • down

  • resolved

  • up

  • unresolved

  • commented

  • assigned

  • deployed

Sample payload sent from Honeybadger


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 { "event": "resolved", "message": "[Crywolf/production] RuntimeError resolved by Joshua Wood", "actor": { "id": 3, "email": "test@opsgenie.com", "name": "Kadir" }, "fault": { "project_id": 1717, "klass": "RuntimeError", "component": "pages", "action": "runtime_error", "environment": "production", "resolved": true, "ignored": false, "created_at": "2015-07-02T18:57:26.757Z", "comments_count": 4, "message": "This is a runtime error, generated by the crywolf app at 2015-07-16 10:44:13 -0700", "notices_count": 3, "last_notice_at": "2015-08-06T22:11:43.738Z", "tags": [], "id": 13760144, "assignee": null } }


Still need help?

The Atlassian Community is here for you.