Skip to main content

Triage Faster

Sailfish's triage workflow gives your team a single screen to understand, prioritize, and act on customer issues — no context switching required.

Triage List​

The Triages page shows all triages created by your team. Triages are created from the Recordings page when someone identifies a customer problem.

Filtering​

FilterDescription
CreatorFilter by who created the triage
Date rangeFilter by when the triage was created

Each triage in the list shows a summary including the number of linked issues and affected sessions.

Triage Detail​

Click a triage to open its detail view. The triage detail has three tabs:

Home Tab​

The Home tab provides an overview of the triaged problem:

  • Problem description — Notes captured when the triage was created
  • Session context — The recording and timestamp where the problem was observed
  • Device info — Browser, OS, screen size, and other device details for the affected session
  • Linked issues — Any issues that have been created from this triage

Engineering Packet Tab​

Same as the Issue Engineering Packet — shows function spans, logs, and exceptions for the triaged session. This gives engineers the full technical context without needing to reproduce the problem.

Occurrences Tab​

Shows whether this same problem has occurred in other sessions. Sailfish automatically identifies similar occurrences to help you understand the blast radius.

Session Playback​

From any triage, you can watch the session replay to see exactly what the user experienced. The replay includes:

  • Full visual playback of the user's screen
  • User interaction markers (clicks, navigation, text input)
  • Error and network failure indicators on the timeline
  • Synchronized console logs and network requests

This is the same replay available in Recordings, focused on the specific moment the triage captures.

Prioritization​

Not all issues are equal. Sailfish helps you prioritize by showing:

  • Affected user count — How many users encountered this problem
  • Severity — Based on error type, user impact, and frequency
  • Recurrence — Whether this is a one-off or a pattern
  • Revenue exposure — Impact on conversion-critical flows

Your team always knows what to fix first.

Taking Action from a Triage​

Create an Issue​

Click Create Issue to promote a triage into a tracked Issue. The issue inherits the triage's context — session, timestamps, and device info — and can then be assigned, tracked, and resolved through the standard issue workflow.

Create an Engineering Ticket​

Directly create a Jira or Linear ticket from the triage. The ticket includes:

  • Full reproduction context from the session
  • Affected user details
  • A link back to the triage in Sailfish

Notify Your Team​

Send a Slack message or email with the triage summary to alert the right people. This is useful when a triage reveals a critical issue that needs immediate attention.

Debugging with Full Context​

Every triage gives you the complete picture without needing to reproduce the problem:

  • User interactions — What the user did leading up to the problem
  • Backend traces — Function calls, database queries, and service-to-service requests
  • Network requests — API calls, response codes, and timing
  • Exceptions and logs — The exact error, stack trace, and surrounding log context