Triage#

When you open Cloud Diagnostics Advanced, you’ll default to the Triage tool for the selected project.

The Triage tool displays crashes or errors grouped by fingerprint (a hash that is generated when processing crashes through Backtrace's deduplication algorithms). The fingerprint is used to signify a unique error with a common root cause.

The Triage tool allows you to filter which errors (fingerprints) you want to view, provides aggregate information about the fingerprint, and enables actions to take to support resolution of the fingerprint. The following actions are available for users to take on fingerprints:

• View and modify the state from Open/In Progress to Resolved and Muted.
• View the Fingerprint and hover to get actions to View the Details page or Open the Fingerprint in the Debug view.
• View the head of the callstack and hover to get a few more lines.
• View the number of occurrences and number of impacted hosts or users, and activity history.
• View system applied tags (classifiers), and manage custom tags.
• View and manage assignees and linked tickets.
• Select multiple fingerprints to take the merge action, or other bulk actions, such as assignment, mute, or resolve.

Fingerprint status#

Each fingerprint has a status of Open, Resolved, In Progress or Muted. These statuses help you know which crashes need analysis, which are being actively worked on, which are resolved, and which can be ignored or muted.

For example, engineering managers can start with open fingerprints to make sure relevant issues are resolved properly, by taking actions such as assigning to an engineer, linking to a Jira issue, and marking as Resolved or Muted.

Notes:

• Fingerprints can be marked as Resolved or Muted using the Status column. Fingerprints that have been marked as Resolved or Muted will stay in that state, to better organize the expected state of instability in your environment.
• A fingerprint is Open if there are no assignees or linked tickets (and has not been marked as Resolved or Muted). The act of assigning a fingerprint or linking it to an issue will cause the Open fingerprint to be listed as In Progress. By the same notion, a fingerprint that is In Progress and has its assignees removed and tickets unlinked will be listed as Open.

Mute or resolve until#

You can take explicit Mute Until or Resolve Until actions on a fingerprint to specify if/when you would like the fingerprint and any linked issues (i.e. Jira) to be reopened. Customers use this capability to specify which criteria should be used to determine if a fingerprint should be re-opened and to automate issue tracking workflows to respond to regressions.

You can specify conditions such as "until the fingerprint is seen in version {choose version attribute} greater than {value}" or "until the fingerprint is seen again after < 30 minutes | 2 hours | 1 day | 1 week | 1 month>".

If the conditions are met, the system sets the state to Open, reopens any linked issues, increments the attribute invariant_reopen_count by 1, and populates the invariant_reopen_last_time with the date and time the fingerprint was reopened. With this information populated, you can build useful views in Triage and Explore to show regressions that were introduced.

Merging fingerprints#

You can select a fingerprint and go to the Similarity page to see candidate fingerprints that are similar. If you see two or more fingerprints that should be grouped together, you can merge them together to create a new fingerprint to group future incoming errors. Unmerge from a fingerprint's Details view.