The new Web Console provides an enhanced interface and interaction model for working with Backtrace. It was developed to support the needs of team members such as Engineers and Engineering Managers, QA and Support personnel, and Business or Product leaders, as they focus on detecting and resolving issues impacting their newly developed or released software.

  • Engineering Managers - Triage the incoming errors (crashes and exceptions), and review the status of assigned errors. Explore, analyze and query the corpus of error data.
  • Engineers - Debug and resolve errors assigned to them. Possibly self-assign errors not yet assigned.
  • QA Personnel - Review the stability of a new release under development, identify regressions that occur and understand new tests required. 
  • Support Staff - Research a problem reported by a customer. Understand if errors have been fixed or what the workaround might be.
  • Business and Product leaders - Understand the overall health of the system. Look for early warning indicators for positive or negative trends.

This document will serve as a guide for using the new Web Console as it enters its public beta phase.

Enable or Disable Access

If the new Web Console is enabled for your organization, you should see a banner for you to opt in. 

  • If you want to be enabled and don't see the banner, please reach out via the chat in the bottom right. 
  • If you see the banner but want to remove it for you or others in your organization, please reach out via the chat in the bottom right.

Set the New Web Console as your Default

After trying the new Console, you can set it as your default.

Getting Around in Console 2.0

Global Header

As you look from upper left to upper right you'll see the following: 

  • Project Selector - use this to switch between various projects that are reporting crashes or errors.
  • Tools - Triage | Explore | List | Debug - These are your top level tools for viewing data in your project. 
  • The Triage tool allows you to see crashes or errors with the most number of occurrences, and allow you to take action, such as assign, link to Jira ticket, and more. 
  • The Explore tool allows you to analyze your error data in customizable ways with powerful group and visualization tools in customizable ways, 
  • The List tool, which allows you to list specific occurrences of errors.
  • The Debug tool, which allows you to view a specific error report, including a symbolicated call stack, system and custom attributes, and other useful information.
  • Utilities - On the far right, you have a link to open Saved Views, which allow you to save common views for easy access, You also have your first initial with a context menu to see Settings and other top level functions (Invite a user, Create a Project) that are available to you.


After selecting your tool (Triage, Explore, etc), you will be able to utilize various filters view the error information that is most important to you.

On the top left, you can add filters identifying crashes from a certain version, a certain user, specific operating system, or more. Filters are available on any system or custom metadata that you provide with your crashes. You can take advantage of powerful filter operators that go beyond the normal equals or contains operators to include not-contains, regular-expression, inverse-regular-expression, at-least, or at-most, depending on the data type. See the image below for examples of the different operators available.

On the top right, you'll see filters for Time Frame. This allows you to filter for issues that have occurred during a certain time period, or when an issue was first seen, which is useful for identifying when specifically an issue may have been introduced.

Shortcut Filters in the Triage Tool

In the Triage tool, you'll notice that errors are automatically grouped by fingerprint, and shortcuts are available to filter on Open, In Progress, Resolved, Muted or All state filters. These states help engineering managers and engineers know which crashes need analysis, which are being actively worked on, which are resolved, and which can be ignored or muted. There is also a shortcut for "Assigned to me" to view crashes that are assigned to the current user.

Result List

After you have selected appropriate filters, you'll be presented with a result list of that is full of information. The Result List will vary depending on which tool you are in. We'll use the Triage tool Result list in the examples below, but make sure to discover the different capabilities offered in Explore and Debug as well.

First, at the top of the Result List, you'll see some informational text that tells you how many issues are being displayed and how many in total there are. This gives you a view of how many additional crashes or errors that are identified outside the filter window.

Depending on which tool you are in, you have additional ways to manipulate the Result List and continue your exploration of Error data.

  • In the Triage tool, you will see errors grouped by Fingerprint. You have various actions available to support resolving the Fingerprint, and you have the ability to open a Details view for the Fingerprint to offer more introspection into the aggregate information about the Fingerprint. 
  • In the Explore tool, you will be able to choose which attributes to Group By, allowing for more more robust exploration of your error data. Users will commonly group by UserID (See impact by user), Host or Device ID (See impact to each host), OS Version (Identify issues encountered after an OS patch), or any custom attributes useful for their application.
  • In the Debug tool, you will be able to navigate through all individual errors that are returned based on the filter conditions. This allows you to iterate through a group of similar errors to identify additional trends or commonalities. 

Next Steps

For next steps in your learning plan, please review the following documentation items:

Did this answer your question?