Skip to main content

Overview

The Triage view is where you review and manage the crashes and errors reported for a project. It opens by default when you open the Web Console.

Instead of listing every error one by one, Triage groups related errors into fingerprints. A fingerprint is a hash generated by Backtrace's deduplication algorithms. It represents one unique error with a common root cause, so you can investigate and track it as a single issue.

Applications can report thousands of errors a day, and many of them come from the same bug. Grouping errors into fingerprints means you work with a short list of unique issues instead. You can see which errors occur most often, who is working on them, and which have already been fixed, then take action to investigate and resolve them.

This section of the documentation covers:

How Errors Are Grouped​

When a crash or error arrives, Backtrace's deduplication algorithms compare it with existing errors. If it shares the same root cause as an existing fingerprint, it is added to that fingerprint. Otherwise, a new fingerprint is created.

As a result, thousands of raw errors can appear in Triage as a short list of fingerprints. For each fingerprint, Triage shows aggregated information, such as how often the error occurs and when it was last seen, so you can decide which fingerprints to investigate first.

What You Can Do in Triage​

From the Triage view, you can:

  • Filter by status: Focus on fingerprints that are Open, In Progress, Muted, or Resolved. See View & Manage Fingerprint Status.
  • Review fingerprint details: Open a fingerprint's Details view to see its attributes, instances, comments, and tags. See View Fingerprint Group Details.
  • Investigate in the Debugger: Open the fingerprint's latest trace to inspect the error and its callstack. See View Fingerprint in Debugger.
  • Assign responsibility: Assign the fingerprint to the user who will investigate or resolve it.
  • Link to an issue: Create a Jira or GitHub issue for the fingerprint to track it outside Backtrace.
  • Add comments and tags: Record investigation findings in comments, and use tags to group and classify fingerprints.
  • Merge related fingerprints: Combine fingerprints that represent the same issue, or unmerge fingerprints that were grouped incorrectly.

For step-by-step instructions on assigning, linking, commenting, tagging, and merging, see Other Actions.