PROACTIVE TROUBLESHOOTING

Segment your errors to focus
on a specific area at a time

From key customers to UI experiments, error segments enable you to focus your view and always come back to refreshed results.

Segment by the application area you're responsible for

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

Keep an eye on key customers

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.

VISIT CUSTOM FILTERS DOCUMENTATION
Search and segment experiments.

Determine the stability of feature flags and experiments

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.

REACTIVE TROUBLESHOOTING

Search is simple when in firefight mode

All the diagnostic data you need to find and reproduce errors centralized in one place accessed by an intuitive search bar.

Find errors that happened to specific users

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:joe@abc-company.com to find every error encountered by a specific user of your app.

Track down slow responses

A slow response can be as detrimental to user experience as encountering an error. Use timeouts to set your performance thresholds.

Find all timeout errors by searching errorClass:Timeout to determine the scope of the performance problem.

DIVE DEEPER INTO USER FRUSTRATION

Real-time error monitoring
for your full stack

SEE SUPPORTED PLATFORMS