Managing event usage

Take control over the events that we save and count towards your event quota

If you send us more events than your Bugsnag plan’s usage quota and you haven’t enabled automatic plan upgrades, some of the events you send us will be intelligently throttled.

This guide walks you through the options you have for configuring Bugsnag to discard certain types of events. By choosing which events to discard, you can avoid throttling and still have Bugsnag save all of the data that matters to you.


Bugsnag uses a number of terms to describe how we handle the events (occurrences of errors) you send us.


  • All of the events that you’ve sent to Bugsnag.
  • You can manage the number of events you send to Bugsnag by configuring the notifier library on any project with Bugsnag installed.


Discarded events are not saved due to your settings. They don’t count against your event usage quota.

Events can be discarded based on a number of criteria:


Throttled events are automatically discarded (not saved) in order to stay within your Bugsnag plan’s event quota.

When you exceed your event quota we intelligently throttle the data you send us. However, if you’d like to avoid throttling altogether you can enable automatic plan upgrades, manually upgrade your plan to raise your event quota, or take steps detailed in this document to prevent overages.

Additionally, in rare cases, if you send us an exceptionally large number of events in a short time window on a single project, some events may be throttled in order for us to maintain to maintain timely event processing for all of our users.


Saved events have been fully processed and any enabled notifications or workflow automations have been triggered. The events are available for viewing in your dashboard and via our data access API.

Notifier library configuration

You can avoid sending Bugsnag particular events by configuring the notifier library on any of your applications that have Bugsnag installed.

The specific options available vary by platform, but most of our libraries provide the ability to ignore errors by release stage, error class, severity or any criteria by using before notify callbacks. See the configuration documentation page for your platform to learn more.

Discard individual errors

Individual errors can be discarded. When discarded, errors are immediately deleted from the dashboard and subsequent events that we receive are not stored.

To discard an individual error:

  • Select Discard from the additional actions menu when viewing an error.

    Discard error

A list of discarded errors on a project can be viewed in Project Settings:

  • In Project Settings, select Discard specific errors.

    Discarded errors

  • To prevent an error from being discarded and start storing it again, click on the X next to the error.

Discard by error class

All events that match named error classes can be discarded. To configure the error classes to discard:

  • In Project Settings select Discard by error class.

  • Enter the names of any error classes to discard separated by new lines, then select Save.

    Discard by class

Discard by app version

All events received from particular versions of your app can be discarded. To configure the app versions to discard:

  • In Project Settings select Discard by app version.

  • Enter the details of the versions of your app to discard, then select Save.

    Discard by version

  • The versions can be expressed as regular expressions and semver ranges. Multiple versions or version ranges can be specified on new lines.

Discard errors from legacy browsers

Errors can be discarded from legacy browser versions or any specified browser versions. This options is available for JavaScript projects only.

To discard errors from legacy browsers:

  • In Project Settings select Discard errors from legacy browsers.

  • Confirm by selecting Discard errors from legacy browsers >.

  • Define individual versions for each browser if required, then select Save.

    Discard by version