Filter your error reports using the filter bar.
The filter bar provides a powerful way to find relevant errors in your dashboard by selecting one or more filter keys and date ranges.
The filter bar automatically updates as you navigate the dashboard to show you the filter keys and date range that corresponds to your current view.
Some filter keys support wildcard or pattern matching, while the date range fields support a flexible syntax.
Exclude filters can be used to remove a subset of errors and events from the view.
Bugsnag provides a filter bar near the top of the screen on each page that allows you to filter your error data.
/. An auto-complete dropdown will appear where you can select your desired filter.
Filter to versions or version ranges using the ‘seen in release’ and 'introduced in release’ filters.
1.*will show errors from all your version 1 releases.
1.0.0will show errors from all versions that were released before 1.0.0 regardless of their version number or name. Note that wildcards are not supported with 'before’ and 'since’.
1.0.0and a versionNumber of
1is displayed as
1.0.0 (1)and can be filtered by using
Add multiple filters to compose complex queries. Filters for different fields will show errors that match all of the distinct filters (boolean AND). Filters for the same field will show errors that match any of the provided values (boolean OR).
For example if you filter on both
user email: test.com and
browser: firefox you will see errors that were experienced by people with a test.com email address that are using Firefox.
If you then added another browser filter
browser: chrome you would see all errors that were experienced by people with a test.com email address while using Firefox or Chrome.
Exclude errors by selecting 'does not match’ when adding a filter value.
The following fields in your error reports are available to use in the filter bar. If you want to filter on something that is not listed below you check out our documentation on custom filters.
|Key||Searches on||Pattern(s) matched||Example(s)|
|User ID||User ID of user(s) affected by an event||Exact match only|
|User email||Email address of user(s) affected by an event||Supports substring matches||bugsnag.com, gmail, jean.bartik@hostname|
|User name||User name of user(s) affected by an event||Supports substring matches||Adele Goldberg|
|Error status||The state of the error in Bugsnag||Exact match only||Open, snoozed, fixed|
|Error assigned to||Collaborator the error is assigned to||“Me”, “anyone”, or exact match||Me, Anyone, Frances Spence|
|Error has linked issue||True/false flag for linked issue||Exact match only|
|Release stage||Production, staging, development, etc.||Exact match only|
|Context||Action happening when the event occurred||Supports substring matches|
|App type||Type of app running when the event occurred||Exact match only||Worker, server|
|Introduced in release||Release/version the error was first seen in||Supports wildcards||
|Seen in release||Release/version the event occurred in||Supports wildcards||
|Error class||The error class of an event||Supports substring matches|
|Error message||The error message of an event||Supports substring matches|
|Filename||Filenames in the event stacktrace||Supports substring matches|
|Method||Methods in the event stacktrace||Exact match only|
|Severity||Error, warning, or info||Exact match only|
|Unhandled||Whether the event was unhandled||Exact match only||True, False|
|Browser||The browser associated with the event||Exact match only||Chrome, Firefox, Safari, Opera, etc.|
|Browser version||Browser version the event occurred in||Supports wildcards:
||45.0.2454.101 (Chrome), 40.0.3 (Firefox)|
|OS||Operating system the event occurred in||Exact match only||OS X, Windows, iOS, Ubuntu|
|OS version||Operating system version the event occurred in||Supports wildcards:
|Hostname||Hostname the event occurred in||Exact match only||staging1, sidekiq|
|Device manufacturer||Manufacturer of the device the event occurred on||Exact match only|
|Device model||Model of the device the event occurred on||Exact match only|
|Request URL||URL of the request that caused an event||Supports substring matches||https://api.example.com/users/|
|Request IP||IP address of the request that caused an event||Exact match only||188.8.131.52, 184.108.40.206|
Don’t see what you want to filter on here? Check out our documentation on custom filters.
Once you have added a set of filters to the filter bar you can easily save the state of the filter bar so that you can access it again at any time. To do this you click the 'star’ icon on the right hand side of the filter bar. You can choose a name for a bookmark and make it the default for the project if desired.
Bookmarks are displayed on the left hand side bar. Selecting one will apply the bookmarked filters.
Saved filters are specific to you so setting the default for the project will not affect your collaborator’s filters.
We use SugarJS to give you a flexible syntax for setting a date or date range filter. The following date formats are supported in the date and date range fields of the filter bar:
20 June 2012
Wednesday, June 20th, 2012
3 days ago
One week ago
A month ago
The end of the month
For an expanded list of date formats, see the SugarJS date syntax documentation.