Backtrace is introducing a new User Experience. We call it Console 2.0, because we’re engineers and couldn’t be bothered to find a flashy name. ¯_(ツ)_/¯
We’ve been talking to the heaviest users of Backtrace for years to help guide product development and prioritize our roadmap. With our latest improvements to the Console, Backtrace fits more seamlessly than ever into common engineering workflows. We focused on reorganizing the interface to provide a steady sense of progress as you:
- Take a look at what crashes or exceptions are happening
- Drill into a specific time frame or filter by version, operating system, device, user, and more
- Triage issues by urgency, assign them to team members, link issues Jira tickets, update the issue status, and more
- Explore crash and exception data through queries like group bys and aggregations and specialized visualizations like flame graphs
- Debug a specific issue with detailed crash reports, dump files, symbolicated callstacks, register and frame details, and more
Across the top you have controls to set the context you work in: the project to look at crashes and exceptions for and filters to apply to the issue list.
In the Triage tool, you:
- Change issue state between Open/In Progress, Resolved, and Muted
- See fingerprint IDs and the head of the call stack
- See the number of occurrences and impacted hosts or users
- See the activity history for an issue
- See Backtrace’s automatic classification of an issue
- Add custom tags to an issue
- Manage assignees and tickets
- Merge issues
- Dig into details about a specific issue
In the Explore tool, you:
- Group by any attributes or tags embedded the crash/exception data, automatically applied by Backtrace, or added by your team
- Aggregate to see counts or distributions of any attribute across all crashes / exceptions
- Use special visualizations like the Flame Graph, which can identify common the codepaths involved in multiple issues
In the Debugger, you:
- Dig into the details of a particular crash or exception
- Get access to dump files and any attachments submitted with the crash / exception
- Step through all the threads
- See relevant state information such as environment variables and modules loaded
- Get a fully symbolicated callstack function names and line numbers
- Step through frame and register details
- And much more depending on the type and format of crash / exception
You can read all the docs on the new interface at the Web Console Overview.
We’re trying to make Backtrace the best platform for cross-platform crash and exception capture and debugging. Try it out and send us your feedback!
The post The New Backtrace UI: Getting Closer to the Jobs to be Done appeared first on Backtrace.io.