Integrations

 

Honeybadger has deep support for a wide variety of third-party services. Let's start by looking at some cool features available for every integration. After that, we'll dive into the specifics of setting up individual services.

Events

You get to choose exactly which events result in a notification or ticket being created:

Events

Rate Escalations

Escalations let you receive extra notifications when your error rate goes above a number you've configured.

Escalation

Throttling

Lets you protect yourself from floods of notifications when everything goes wrong at once.

Throttling

Filters

With filters you can be hyper-precise about which errors trigger notifications or issue creation. You could

  • Send alerts to a special chatroom if an error is caused by your CEO
  • Create issues in separate trackers for staging, preprod and production
  • Route notifications to a certain team's inbox whenever an error assigned to that team reoccurs.

Filters

Environments

You can ignore environments. We auto-populate the list based on environments we've seen in your app.

Environments

Services

Asana

1. Select the Asana integration

asana integration

asana integration

2. Enter your API key

To get your Asana API key, go to Asana and do the following:

  • Click your profile photo from the top bar and select My Profile Settings
  • Navigate to the Apps tab
  • Select API Key

3. Enter your workspace id

To get your Workspace ID, log into Asana and go to https://app.asana.com/api/1.0/workspaces. This will give you a JSON object which contains your workspaces along with their IDs.

4. Enter your project id (optional)

You can optionally enter a Project id, if you want all tasks created by Honeybadger to belong to a specific project.

You can get your project's ID by looking at its Asana URL. It will be the first string of numbers directly after the /0/. For example if the URL is https://app.asana.com/0/3333333333333/777777777777 that means your project id is 3333333333333.

Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




Bitbucket

1. Select the Bitbucket integration

bitbucket integration bitbucket integration

2. Set the repository name

The repository name includes the account name. For example, Honeybadger has a repo called "docs" the repository name we'd enter here is "honeybadger/docs".

3. Authenticate

Click "Save and Authenticate With Bitbucket" to complete setup. This will send you to bitbucket.org to authenticate via OAuth.




Campfire

1. Select the Campfire integration

campfire integration campfire form

2. Set the API key

To get your Campfire API key, log into campfire and go into the "My Info" page. Then click on "Show your tokens." More info

3. Set the Subdomain

If you go to honeybadger.campfirenow.com to log into campfire, you'll enter "honeybadger" here. No need to enter the full domain name.

3. Set the Room

This is the name of your chatroom. It needs to exactly match the name you see on screen.

4. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




Clubhouse

1. Set the organization

This is the name of the organization that you created when you set up your account. You can find this immediately after the domain name in the URL: e.g., for https://app.clubhouse.io/honeybadger the organization name is honeybadger.

2. Set the API Token

Your API Token can be found in the Clubhouse UI by clicking on the gear icon for settings, choosing the Your Account link, then choosing the API Tokens link. Choose a name for your token (like Honeybadger) and click Generate Token. Copy the highlighted token, and paste that in the API Token field.

3. Fetch project info

Click the Fetch project info button to make a request to the Clubhouse API to get your list of projects and workflow states. This will populate and enable the remaining checkboxes on the form.

4. Choose the project and workflow states

Each Honeybadger project is associated with one Clubhouse project, and you can make that choice here. You can also choose which of your Clubhouse workflow states will be chosen for stories when they are marked as resolved or unresolved. The stories will be updated to those states if you also enable the respective Error Events options.

Creating stories from the UI

Users can create stories in Clubhouse by clicking the Create Story button on the error detail page in the Honeybadger UI. By default, these stories will be created as the Clubhouse user whose API Token is configured in the integration settings. Users can have stories associated with their own Clubhouse account by getting an API Token as described previously and adding it to their authentication settings.




DataDog

1. Select the DataDog integration

pagerduty integration pagerduty form

2. Set the API key

You can generate a DataDog API key on the DataDog integrations page.

3. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




Email

Heads Up! This isn't where you configure your personal email notifications. This email channel is specifically for integrating with services like Basecamp which consume inbound email.

1. Select the Email integration

email integration email form

2. Enter the email address

It's just an email address, folks. I'm sure you can figure it out. :wink:

3. Save

That's it! Just save and you're ready to go.




Flowdock

1. Select the Flowdock integration

flowdock integration flowdock form

2. Set the API key

You can get your Flowdock API key by logging into Flowdock, then going to Account > API Tokens.

3. Enter tags (optional)

If you'd like us to tag errors we send to Flowdock, just enter a comma-separated list of tags here.

4. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




Github

1. Select the Github integration

github integration github form

2. Set the repository name

The repository name includes the account name. For example, Honeybadger has a repo called "docs" the repository name we'd enter here is "honeybadger/docs".

3. Enter labels (optional)

If you'd like us to label issues we create in Github, just enter a comma-separated list of tags here.

3. Authenticate

Click "Save and Authenticate With GitHub" to complete setup. This will send you to github to authenticate via OAuth.




HipChat

1. Select the HipChat integration

hipchat integration hipchat form

2. Set the repository name

You can create a HipChat API token by logging into HipChat and visiting the API Tokens page.

3. Set the room

This is the name of your chatroom. It needs to exactly match the name you see on screen.

4. Use a custom HipChat server (optional)

If you have a self-hosted version of HipChat, you can enter its url here and we'll use it.

5. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




Intercom

1. Select the Intercom integration

intercom integration

intercom form

2. Enter your APP ID and API key

To get your APP ID and API key, go to Intercom and do the following:

  • Hover over your profile photo at the bottom of the left bar and select App Settings
  • Navigate to the API Keys tab
  • Grab your APP ID and API Key (or create a new "Full Access" API Key)

4. Enter your context field

This is the field that you set in the context in your application with the user ID that is associated with your Intercom users. For example, if you are identifying users with Intercom with current_user.id, and you have current_user.id in the user_id field of your context, then enter user_id in this field.

Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




Jira

Honeybadger only works with "Software Development" projects on Jira. This is because of the "issue types" we send, which are "bugs".

1. Select the Jira integration

jira integration jira form

2. Configure

Here's an overview of the options:

  • The username and password will be your login for Jira.
  • The server url is the subdomain of your Jira instance, such as "https://hb4lyfe.atlassin.net". Don't forget the "https://".
  • The project key was setup when you created the project. It can be found (on Jira) from Project Overview > Administration > Edit Project.
  • The transition ID's can be set in your workflows on Jira when viewed in text mode. ID's are unique, so make sure there are no conflicting values.

3. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




OpsGenie

1. Select the OpsGenie integration

pagerduty integration pagerduty form

2. Set the API key

You can generate a OpsGenie API key by logging in to OpsGenie then clicking on "Settings". Here's a detailed walkthrough.

3. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




PagerDuty

1. Select the PagerDuty integration

pagerduty integration pagerduty form

2. Set the API key

You can generate a PagerDuty API key by logging in to PagerDuty then clicking on "Add New Service" and choosing "Honeybadger" as the service type. Here's a walkthrough.

3. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




Pivotal Tracker

1. Select the Pivotal Tracker integration

pivotal integration pivotal form

2. Set the API key

You can find your Pivotal Tracker API key by logging in to Pivotal and visiting your profile page.

2. Set the project id

You can find your project's id by examining the URL. If your project's url is pivotaltracker.com/projects/777 then the project id is "777".

3. Enter labels (optional)

If you'd like us to label the stories we create, just enter a comma-separated list of labels here.

4. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




Redmine

1. Select the Redmine integration

redmine integration redmine form

2. Set the server & API key

The server URL is the full URL of your server - including https://.

You can find your API key on your account page when logged into Redmine

3. Configure transitions (optional)

You can specify the ids of transitions to be run when issues are resolved and reopened.

4. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




Slack

1. Select the Slack integration

slack integration slack form

2. Set the webhook URL

To get this, log into slack and click "Add a Service Integration." Find the "Honeybadger" integration and click "Add." You'll be given the URL at this point.

It's important that you use Slack's Honeybadger integration. If you try to use a generic slack webhook URL, it won't work.

4. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




Sprintly

1. Select the Sprintly integration

sprintly integration sprintly form

2. Set the email & API key

You can get your Sprintly API key by logging into Sprintly and going to your Profile page. The key is at the bottom.

3. Set the product id

You can find your product's id by examining the URL. If your product's url is sprint.ly/product/777 then the product id is "777".

4. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




Trello

1. Select the Trello integration

trello integration trello form

2. Connect your Trello Account

Just click the button to connect to trello via OAuth.

3. Select the board and list

These two dropdowns will be populated when you connect your account.

4. Save

That's it! Hit save and you're good to go.




VictorOps

1. Select the VictorOps integration

pagerduty integration pagerduty form

2. Set the API key

You can generate a VictorOps API key on the VictorOps integrations page.

3. Set the routing key (optional)

If you like, you can specify an arbitrary routing key for use by Victorops.

4. Save

That's it! You can test the integration by clicking "Test". Otherwise, just save it and you're ready to go.




WebHook

1. Select the WebHook integration

webhook integration webhook form

2. Set the URL for your webhook

We'll post notifications to this URL. Make sure to include the protocol: e.g., https://mysite.com/hook.

Make sure you have a service running that can accept POST requests, and hopefully do something interesting with JSON payloads like this one:

{
  "event":"occurred",
  "message":"[Crywolf/test] RuntimeError - oops",
  "fault":{
    "id":3151009,
    "project_id":1717,
    "klass":"RuntimeError",
    "component":null,
    "action":null,
    "environment":"development",
    "resolved":true,
    "ignored":false,
    "created_at":"2014-01-08T18:55:48Z",
    "comments_count":1,
    "message":"oops",
    "notices_count":9,
    "last_notice_at":"2014-01-08T19:02:21Z"
  }
}

3. Save

That's it! Hit save and you're good to go.