Honeybadger has deep support for a wide variety of third-party services. This page provides an overview of some cool features available for every integration. Our list of services has details on setting up individual services.
You get to choose exactly which events result in a notification or ticket being created:
Escalations let you receive extra notifications when your error rate goes above a number you've configured.
Lets you protect yourself from floods of notifications when everything goes wrong at once.
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.
You can ignore environments. We auto-populate the list based on environments we've seen in your app.
For the personal email settings and for the email integration, you can customize the subject line for notifications about errors: when an error is reported, assigned, marked as resolved, etc. The following tokens can be used to customize the subject line:
|[project]||The project name|
|[environment]||The operating environment — production, development, etc.|
|[type]||The event type — occurred, assigned, etc.|
|[class]||The class of the error associated with the event|
|[fault_id]||A unique id for the fault event|
|[file]||The filename with path and line number where the error occurred|