Email notifications

Learn how to set up notifications for BugSnag.

Email notifications deliver information about errors in your apps straight to your inbox.

Receive notifications in other tools by setting up an integration. Learn more >

Configure email notifications

Set up the email notifications by selecting My email notifications from Settings, or My email notifications from your project settings.

Email notifications are set up individually by each collaborator.

Notification configuration can be shared by all projects, or each project can be configured individually. To switch, select Configure notifications from the email notifications settings.

Shared or individual project configuration

Stability summary emails

Receive a daily or weekly stability summary to track your project’s progress against your stability targets. The summary also includes the most frequently occurring new errors, recent team activity, and more. The weekly email is sent every Monday.

You can opt to always receive the summary, or only when the stability score drops below your stability target or critical stability.

Notification filters do not impact these emails.

To set up, select Stability summary from the email notification settings.

Project summary

Stability features are available on Preferred and Enterprise plans.

Performance summary emails

If you are sending Performance trace information to BugSnag, you can receive Performance summary emails. See Performance notifications for details.

Configuring notifications

Select the notifications that you want to receive from the Notify me when section. The following notification types are available:

Project notifications

  • This project has a spike in errors will notify you when there is an overall spike in all the errors that match your filter. Learn more >
  • This project has a new release will notify you every time a new release in a selected release stage is detected either from a received session or error, or reported to the Build API.
  • This project is being rate-limited will notify you each day when your project is being rate-limited, if you have chosen rate limiting for when you have an event overage.
  • This project is close to being rate-limited will notify you when your project is close to being rate-limited, up to once per 2 hour period. This notification is available if you have chosen rate limiting and have a Standard or Enterprise plan.

Error notifications

  • A new error occurs will notify you if the first event of an error (per release stage) matches your filters.
  • An error occurs frequently will notify you when an error receives x events, or impacts x users, in y hours that match your filters, where you can define the number of events/users (x) and the time interval (y). A maximum of one notification will be triggered per time interval (y).
  • An error milestone is reached will notify you when the number of events of an error (per release stage) reaches a milestone, and the event matches your filters. The milestones are the 10th, 100th and 1000th events and then every subsequent 1000th event.
  • Every time an error occurs will notify you every time an event matching your filters is received.
  • An error is automatically reopened will notify you when an error that has been marked as fixed or snoozed (and matches your filters) receives an event that causes the error to be reopened.

Collaborator notifications

  • A collaborator comments on an error will notify you when a collaborator on your project adds a comment to an error that matches your filter.
  • A collaborator changes the state of an error will notify you when a collaborator on your project manually changes the state of an error that matches your filter, for example marking an error as fixed.

Notification settings

Filter settings

Notifications can configured using Basic filters or Advanced filters.

Basic Filters

Basic filtering for notifications is provided for severity, type, and release stage.

  • Filter by release stage: Select the release stage(s) that you want to receive notifications about from the Release stage dropdown.
  • Filter by type: Receive notifications for either handled or unhandled errors only. Find out more >
  • Filter by severity: Select the severity option(s) that you want to include in your filter from the Severity toggle.
  • Filter by status: Select the status option(s) that you want to include in your filter from the Status toggle.

Basic Filters

Advanced filters

Advanced filtering leverages saved filtersets to enable you to filter a notification based on any field you can filter on using the filter bar. Advanced filtering is available on Preferred and Enterprise plans.

  1. Create desired filters using the filter bar: From the Inbox or Timeline, create filters to match the errors you want to receive notifications for. Learn more >
  2. Save filterset: Select + Save current filterset and set an appropriate name. Select Share this filterset with my team if this filterset is being used for an integration. Email notifications can use either personal or shared filtersets.
  3. Select the saved filterset for your notification: Open the configuration for your desired notification, select Advanced filter, and pick the filterset that you created.

Examples

Some ideas for useful notifications include:

  • New errors in a release: Create a filterset for errors introduced in your desired release, and configure a notification when a new error occurs.
  • There is a spike in errors for your most valuable users: Create a filterset matching errors that occur for your most valuable users, and configure a notification when this project has a spike in errors.
  • An error assigned to someone in your team starts occurring frequently: Create a filterset matching errors that are assigned to any collaborator in your team, and configure a notification when an error occurs frequently.

Email commands

Actions such as changing the status of an error or adding a comment can be performed by replying to error notification emails. See the email commands for details.