Triaging and debugging your error data and crashes often requires more than just intelligent deduplication, analysis of appropriate contextual information, and deep introspection into system state. It also requires the ability to search, explore and discover fine-grained patterns that may exist across all your error data.
Most tools hamper your ability to perform this discovery, limiting the amount of data collected through event sampling, (sampling the data so you can’t be sure that you see every error a specific user encounters) or by not providing a search engine and data visualization tool.
Backtrace is different. We are on a mission to liberate your diagnostic data, and have developed a set of powerful indexing, query and visualization features to ensure that our users can find any individual error they are looking for, within the entire set of data they have collected.
We combine these features into a tool we call the Query Builder. It allows you to filter, group and aggregate across the detailed treasure trove of the system information that is collected alongside errors and crashes. Let’s take a few moments to explore how our customers are using Query Builder today.
Group and View Error Data and Crash Reports Based on Context
Engineers and managers turn to Backtrace to group their crash reports by dimensions other than similarity score. They need to group and aggregate error data based on context. They can answer questions like, “What is the impact by affected users?” or “How does instability compare across OS versions?” Release Managers Want The Query Builder tool exposes simple to use Group By and Aggregate functions that allow for this powerful faceting.
Search the Stack Trace
Engineering and QA teams use Backtrace to search for issues that may (or may not) have commonly affected stack traces or fault addresses. Below, we show how Backtrace allows you to use operators such as contains, not-contains, or regex to filter by various attributes and search across functions and modules referenced in call stacks.
Know Every Error Your Users Encounter
Game Developers or Support Teams, need to identify specific errors that occur for individual users. In the image below, you can see how this team is able to capture and report on every single individual error, and group by username to identify the specific instabilities that a given user has seen. They can then drill into a sortable list of every error, and can further launch Debugger sessions to help them get a better understanding of the system context at the time of the error.
Are you a Backtrace user who has found other innovative ways for searching through your diagnostic data? Let us know! And if you can’t do this with your error management tools today, you should consider trying Backtrace for 30 days free now.