We’re excited to announce the release of Advanced search in Bugsnag—the newly simplified search bar and search builder that make it easier to use Bugsnag’s powerful data segmentation capabilities. With Advanced search, you’ll gain observability into your application through a personalized view of your data.
Advanced search lets you quickly hone in on the errors most impactful to your users using various search features.
All of these features are easily discoverable in the search bar and will help you create data segments for investigation into your application’s stability. And from the personalized segments you create, you can more effectively prioritize important errors and ensure your users’ experience is up to your standards.
Product teams rely on Bugsnag because it takes error data and translates it into something actionable, and one of the ways it does this is through powerful search and segmentation. Especially for teams working in high-volume applications, the volume of data makes it difficult to understand an application’s stability in production and identify problematic errors. Without real observability, the ability to prioritize engineering time for bug fixes and feature building is a guessing-game.
That’s what makes Advanced search so valuable—product teams can make data-driven decisions about fixing errors or building features for their users when they have observability into their application. Observability comes from the ability to create personalized views of the data they care about, so they can easily digest the information and take action.
Tightly coupled with search is the ability to have all your data stored in one place. The reason for this is that by collecting all your data, Bugsnag can give you accurate error counts, so you know definitively (not just on average) which errors happen most and impact the most amount of users. This is also true when using search to create a segment, so you’ll get this level of accurate information, even from a drilled down view of your data.
This precise information helps in decision making since there’s no question which errors have the greatest impact and need to be prioritized.
In this update, we’ve aimed to simplify search and make many of the granular search capabilities more discoverable. Here’s a overview of these changes and the ways you can take advantage of them.
There are three main filters that are used most frequently and are now easily accessible: Stage, Release, and Severity. They are located at the top level since they will likely apply to any search you create. The quick filters UI was designed so you can easily filter to see error segments like:
The quick filters can be combined with other search attributes to hone in your view of error data even further.
Bugsnag now supports simple text search so you can quickly type in an email address, error name, etc. and return matches automatically. For quick searches, this is a fast and easy option.
You can also use simple search to create a segment based on multiple search attributes. To do this, type in a combination of key/value pairs into the search bar. For example, a user experiences an error on your sign-in page and writes into support to report it. You can type in userID:SallyBugsnag context:sign_in and Bugsnag will return all errors this user experienced on that page in your application.
To create data segments for viewing a personalized view of your errors, use the search builder. You can combine various filters related to the stacktrace, user, environment, and workflow status, in addition to any quick filters you’ve set.
Bugsnag captures error details automatically, but since every application is unique, you can also add custom metadata to error reports for additional context. For example, you can add the subscription level or plan name of the user who experienced the error.
You can then create a custom filter for this metadata to search for all errors that affect a certain plan name, a segment that’s unique to your application.
Advanced search is a powerful and unique way to get the level of observability needed to make decisions about bug fixes versus feature building. By segmenting your data to bring the most important information to your view, while ignoring the rest, you can take ownership over your area of responsibility within your application. All of this is aimed at helping product teams ensure the stability of their product so they can deliver a great user experience.