Take control over which events we save and count towards your event quota.
Bugsnag plans come with a daily quota on the number of events we capture and save. We provide two options for handling daily event quota overages, capture every event and sampling.
Whichever event overage strategy you prefer, take control of which events we save to get the most out of Bugsnag.
Bugsnag uses a number of terms to describe how we handle the events (individual occurrences of errors) you send us.
‘Received’ refers to all events you send to us from your Bugsnag notifier library.
You can configure your Bugsnag notifier library to control which events get reported from your app to be 'received’ by Bugsnag. Most of our libraries provide the ability to ignore errors by release stage, error class, severity or any other criteria by using
before notify callbacks. See the configuration documentation page for your platform to learn more.
'Discarded’ refers to events that are not saved due to your in-app settings. They don’t count against your daily event quota.
Events can be discarded based on a number of criteria:
'Dropped’ refers to events that are not processed in order to stay within your Bugsnag plan’s daily event quota when sampling is enabled.
In rare cases, if you send us an extraordinarily large number of events on a single project in a short period of time, some events may be dropped in order for us to maintain to maintain timely event processing for all of our users.
'Saved’ refers to events that have been fully processed. Saved events have the potential to trigger enabled notifications and workflow automations. Saved events can be viewed in your dashboard and via our data access API.
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.
A list of discarded errors on a project can be viewed in Project Settings:
In Project Settings, select Discard specific errors.
To prevent an error from being discarded and start storing it again, click on the X next to the error.
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.
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.
The versions can be expressed as regular expressions and semver ranges. Multiple versions or version ranges can be specified on new lines.
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.