--- title: Integrations description: Send Honeybadger data to other services. url: https://docs.honeybadger.io/guides/integrations/ --- Honeybadger has deep support for a wide variety of [third-party integrations](https://docs.honeybadger.io/guides/integrations/#supported-integrations). This page provides an overview of some cool features available for every integration. These settings are located at **Project settings > Alerts & integrations**. You can click the edit icon and customize the notifications for each integration. ![Project settings showing Alerts & integrations navigation](https://docs.honeybadger.io/_astro/alerts-and-integrations-nav.k9DyuVEM_1v3wdr.webp) ## Customizing integration notifications ### Errors ![Error event options](https://docs.honeybadger.io/_astro/channel_event.CpHSZMFm_Z3PpVm.webp) You get to choose which error events result in a notification or ticket being created: ### Uptime checks You can edit which uptime events are sent to the integration for all or a subset of the project’s uptime checks: ![Uptime](https://docs.honeybadger.io/_astro/channel_uptime.BERsvy7X_uXiFo.webp) ### Check-Ins And you can also change what check-in events are reported: ![Channel check-in options](https://docs.honeybadger.io/_astro/channel_check-in.TvVWRVEX_26BCvX.webp) ### Environments You can ignore environments. We auto-populate the list based on environments we’ve seen in your app. ![Error environment options](https://docs.honeybadger.io/_astro/channel_environment.D4pLEOuX_1TDibo.webp) ## Rate escalations Escalations let you receive extra notifications when your error rate exceeds a number you’ve configured. ![Escalation](https://docs.honeybadger.io/_astro/channel_escalation.DzkFbqJD_Z1LEHBV.webp) ## Error volume anomaly detection Anomaly detection alerts you when a project’s **total error volume** deviates from its learned baseline. Unlike [rate escalations](https://docs.honeybadger.io/guides/integrations/#rate-escalations), which fire at a fixed threshold you have set, anomaly detection learns each project’s normal hourly error volume and notifies you when the current rate is statistically unusual (for example, “errors are 4.7× your normal rate”). Turn it on per integration in the **Anomaly detection** section in the integration’s options. Honeybadger evaluates your projects every few minutes and sends a single notification when a spike begins. A two-hour cooldown then suppresses repeat alerts so a sustained spike notifies you once rather than continuously. Anomaly detection needs enough history to learn what’s normal — at least 48 hours of error activity. Brand-new or very quiet projects won’t trigger alerts until they’ve accumulated enough data. Spike alerts go to notification and alerting integrations (email, Slack, SMS, PagerDuty, Opsgenie, Microsoft Teams, webhooks, and similar). Issue-tracker integrations (GitHub, Jira, Linear, and the like) don’t receive spike alerts, since a spike is an alert rather than a fileable issue. See the structure of the JSON sent to webhook and event-based integrations in the [`volume_spike`payload](https://docs.honeybadger.io/guides/integrations/payloads/volume_spike/). ## Throttling Avoid floods of notifications when everything goes wrong at once. ![Throttling](https://docs.honeybadger.io/_astro/channel_throttle.DTGlCAas_1WwfJy.webp) ## Filters With filters, you can be hyper-precise about which errors trigger notifications or issue creation. You could: * Create issues in separate trackers for staging, prepared and production * Route notifications to a certain team’s inbox whenever an error assigned to that team reoccurs. ![Filters](https://docs.honeybadger.io/_astro/channel_filter.BkRvfP-j_11DXUs.webp) The syntax for error filters is essentially the same as our search syntax, with a few limitations: * You can’t filter on params, context, session or other per-notice data * Filters don’t support freeform text search. You must use the `key:val` syntax. Below is a list of fields you can use when constructing your queries. Note that you can prefix any query with `-` to create its inverse. | Example query | Matches | | ------------------------------- | ------------------------------------------ | | `is:resolved` | Resolved errors | | `is:paused` | Paused errors | | `is:ignored` | Ignored errors | | `assignee:"nobody"` | Unassigned errors | | `assignee:"anybody"` | Errors assigned to anyone | | `assignee:"jane@email.com"` | Errors assigned to a specific person | | `environment:"production"` | Errors occurring in production | | `class:"PermissionDeniedError"` | Errors with a certain class | | `tag:"tag_example"` | Errors with a tag | | `message:"404"` | Errors with a message | | `component:"UsersController"` | Errors occurring in a controller/component | | `action:"update"` | Errors occurring in an action | Multiple filters are evaluated using a logical OR. If any query matches the error, a notification will be sent. When using negative queries like `-class:Foo`, this OR behavior can give unexpected results. To combine multiple negative matches, use a single filter with a search term like `-class:"Foo" AND -class:"Bar"`. ## Custom formatters For some of our integrations, we allow the option to provide a custom format for specific fields (e.g., email subject line or Trello card title). Your custom format will be used for all events that are applicable for the integration (reported, assigned, marked as resolved, etc). The following is a list of valid formatter tokens: | Token | Description | | --------------- | ----------------------------------------------------------------------------------- | | `[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 | | `[message]` | The message of the error associated with the event | | `[component]` | The component name (might be null, usually maps to the controller name) | | `[action]` | The action name (might be null, usually maps to the controller action e.g. `index`) | | `[fault_id]` | A unique id for the fault event | | `[file]` | The filename with path and line number where the error occurred | | `[backtrace]` | The backtrace of the error associated with the event (first 3 lines) | | `[url]` | The URL of the event in the Honeybadger UI | ## Supported integrations Your Honeybadger data can be sent to a variety of third-party services, listed below. We support creating issues for errors in the SCM and project management tools, such as GitHub and Jira. For communication tools like Slack and PagerDuty, we can send notifications for errors, sites that go down (and come back up), and check-ins. [![alertops.png](https://docs.honeybadger.io/_astro/alertops.N4aLK7Tw.png)AlertOps](https://docs.honeybadger.io/guides/integrations/alertops/)Send alerts to AlertOps [Asana](https://docs.honeybadger.io/guides/integrations/asana/)Create Asana tasks from errors [Backlog](https://docs.honeybadger.io/guides/integrations/backlog/)Create Backlog issues from errors [Bitbucket](https://docs.honeybadger.io/guides/integrations/bitbucket/)Create Bitbucket issues from errors [Campfire](https://docs.honeybadger.io/guides/integrations/campfire/)Send notifications to Campfire [ClickUp](https://docs.honeybadger.io/guides/integrations/clickup/)Create ClickUp tasks from errors [ClickUp Chat](https://docs.honeybadger.io/guides/integrations/clickup-chat/)Send messages to ClickUp Chat [Datadog](https://docs.honeybadger.io/guides/integrations/datadog/)Send events to Datadog [Discord](https://docs.honeybadger.io/guides/integrations/discord/)Send notifications to Discord [Email](https://docs.honeybadger.io/guides/integrations/email/)Receive email notifications [GitHub](https://docs.honeybadger.io/guides/integrations/github/)Create GitHub issues from errors [GitLab](https://docs.honeybadger.io/guides/integrations/gitlab/)Create GitLab issues from errors [Google Chat](https://docs.honeybadger.io/guides/integrations/google-chat/)Send messages to Google Chat [![ilert.png](https://docs.honeybadger.io/_astro/ilert.CXUfRGif.png)ilert](https://docs.honeybadger.io/guides/integrations/ilert/)Create ilert alerts [incident.io](https://docs.honeybadger.io/guides/integrations/incident-io/)Create incidents in incident.io [Instatus](https://docs.honeybadger.io/guides/integrations/instatus/)Update Instatus status page [Intercom](https://docs.honeybadger.io/guides/integrations/intercom/)Send messages to Intercom [Jira & Jira Cloud](https://docs.honeybadger.io/guides/integrations/jira/)Create Jira issues from errors [Linear](https://docs.honeybadger.io/guides/integrations/linear/)Create Linear issues from errors [Mattermost](https://docs.honeybadger.io/guides/integrations/mattermost/)Send notifications to Mattermost [Microsoft Teams](https://docs.honeybadger.io/guides/integrations/microsoft-teams/)Send messages to Microsoft Teams [OpsGenie](https://docs.honeybadger.io/guides/integrations/opsgenie/)Create OpsGenie alerts [PagerDuty](https://docs.honeybadger.io/guides/integrations/pagerduty/)Create PagerDuty incidents [PagerTree](https://docs.honeybadger.io/guides/integrations/pagertree/)Create PagerTree alerts [Redmine](https://docs.honeybadger.io/guides/integrations/redmine/)Create Redmine issues from errors [![rootly.png](https://docs.honeybadger.io/_astro/rootly.CnXPv3q1.png)Rootly](https://docs.honeybadger.io/guides/integrations/rootly/)Create Rootly incidents [Shortcut](https://docs.honeybadger.io/guides/integrations/shortcut/)Create Shortcut stories from errors [Slack](https://docs.honeybadger.io/guides/integrations/slack/)Send notifications to Slack [Splunk On-Call](https://docs.honeybadger.io/guides/integrations/splunk-on-call/)Create Splunk On-Call incidents [![sprintly.png](https://docs.honeybadger.io/_astro/sprintly.Bm6r2OKO.png)Sprintly](https://docs.honeybadger.io/guides/integrations/sprintly/)Create Sprintly items from errors [Trello](https://docs.honeybadger.io/guides/integrations/trello/)Create Trello cards from errors [Webhook](https://docs.honeybadger.io/guides/integrations/webhook/)Send webhooks to custom endpoints [Zulip](https://docs.honeybadger.io/guides/integrations/zulip/)Send messages to Zulip --- ## Try Honeybadger for FREE Intelligent logging, error tracking, and Just Enough APM™ in one dev-friendly platform. Find and fix problems before users notice. [Start free trial](https://app.honeybadger.io/users/sign_up) [See plans and pricing](https://www.honeybadger.io/plans/)