Find the errors that matter using the search bar.
The search bar provides a powerful way to find relevant errors in your inbox and timeline, and relevant events of an error on the error details page.
The search bar has the following elements:
Use the release stage filter to show errors from specified release stages.
A release stage is the environment that your application is running in, such as production, staging or development. Find out more about setting the release stage.
Use the release/version filter to show errors from specified releases/versions.
Releases are generated when Bugsnag detects a named version of your application is running in a release stage. Find out more about setting your app version.
Use the severity filter to show errors that were unhandled by your application code or are of specific severity.
Find out more unhandled errors and severity in the severity indicator docs.
errorseverity errors which have the biggest impact on your users.
Get to the search box quickly using the keyboard shortcut
Type any string to search across common fields for matching errors.
Try these examples:
BadException- find errors with a type or error class of BadException.
MyCodeFile.java- find errors where the stack trace includes stack frames from MyCodeFile.java.
mycustomer.com- find errors impacting users with a @mycustomer.com email address.
Select Search builder to precisely specify the fields you want to match errors on. The available fields are split into five tabs: Stacktrace, Workflow, User, Environment & Custom Filters. If you want to search on a field that is not available by default you can add a custom filter. See the custom filter docs for details.
Search by properties of the code where the error originates, such as the error class, error message or the filenames and methods of the code running at the time of the error.
Find errors based on their progress through the Bugsnag workflow, including their status and which collaborator they are assigned to.
Discover errors affecting certain users of your app, identified by their ID, email or name. See your platform’s docs to add this information to your error reports.
Search on properties of the environment where your application is running. Depending on the type of your app this could be information about the browser, mobile device or server where the error occurred.
Filter errors by custom fields to analyze problems critical to your business, like bugs seen by key customers, or in A/B tests. See your platform’s docs to find out how you can add custom attributes (metadata) to each error or find out more about custom filters.
Alternatively you can perform advanced searches directly in the search box using the
key:value syntax where:
:to search for matching values, or
:!to search for values that do not match.
Try these examples:
userEmail:bugsnag.com- find errors the happened for users with a bugsnag.com email address.
errorClass:!Timeout- find all the errors where the error class isn’t a timeout error.
myCustomerType:vip- find the errors affecting VIP customers as defined by you and using a custom filter.
Use the date & time filter to show recent errors that occurred in the last hour, day, week or month, or choose a specific date range.
Once you have selected a set of filters and search criteria you can easily save the state of the search bar so that you can access it again at any time. To do this you click the 'bookmark’ icon on the right hand side of the search bar and select Create new bookmark. You can choose a name for a bookmark and make it your default for the project if desired.
Switch to a different bookmark using the same button, or select one from the list displayed on the left hand side of the inbox.