Surface the errors most relevant to you or your team by bookmarking a segment of errors. For example, segment errors on the latest release and from a critical section of your application, like errors in your customers' shopping cart.
Build a segment with the release filter set to latest and context:shopping_cart
There are customers that are critical to your business. Improve stability for key customers by segmenting errors by spend, SLA, or subscription tier.
Use a custom filter similar to myCustomerType:vip to segment errors on VIP customers.
Customize alerts to be notified of errors in your segments, such as those occurring in your codebase, in a critical section of your application, or affecting VIP customers.
Use alerts to decide which errors to prioritize and fix, drive code ownership, and accelerate DevOps workflows around incident investigation and resolution. Integrations with team chat, issue tracker, and incident management tools help reduce the time it takes from error detection to resolution.
Experimental features are awesome until they aren’t. It is important to assess whether an individual feature or experiment is introducing new errors in your application before rolling it out to all users to ensure a streamlined user experience.
You can easily segment errors happening in feature flags, A/B tests and experiments by creating a custom filter for arrays in Bugsnag.
Quickly tie a support ticket with a user to see exactly the errors they encountered, no more tedious email threads to get error context.
Search by user ID or email userEmail:firstname.lastname@example.org to find every error encountered by a specific user of your app.