Finding the errors that matter with issues

Updated

Issues groups the errors that Strabber records on your site, so the same error is one row instead of hundreds. Each issue shows how many times it happened, how many visitors ran into it and whether it's getting better or worse. You can then resolve it once it's fixed, or ignore it if it doesn't matter.

Issues are built from the script errors and console errors on the Logs and errors page, so you don't need to add any code. Console logs, warnings, info and debug messages aren't grouped into issues.

How errors are grouped

Errors are one issue when they have the same type (script error or console error), the same message and, for script errors, the same script file. Parts that change from one visitor to the next are left out, so these are one issue:

  • Payment failed for order #1042 and Payment failed for order #2817
  • The same error in app.3f9c2a1b.js and in app.8d41e07c.js after a new release
  • The same error in checkout.js?v=12 and in checkout.js?v=13

Numbers, IDs, links and the query string of the script are left out. The line and column aren't part of an issue either, so an error stays one issue when your code moves.

Issue IDs

Every issue gets an ID the first time its error happens, such as IS-2026-001: the year it first happened and a number. Numbers start at 001 for each project and go up across all of the project's websites, and an issue keeps its ID for good.

Use the ID to talk about an issue with your team, or to put it in a commit message or a ticket. The ID is also in the address of the issue's page, such as /issues/IS-2026-001, so you can share the link with anyone who has access to the site.

The list

Open Issues in the sidebar. The list shows the issues that happened in the period, with:

  • Issue: the latest message, the issue ID, its type, who it's assigned to and its script file and line
  • Trend: how many times it happened each day of the period
  • Events: how many times it happened in the period
  • Visitors: how many visitors ran into it in the period
  • Last seen: when it last happened

An issue first seen in the period is marked New. Choose the Period at the top, or click 7 days, 30 days or 90 days. The period, the status, sorting and search stay at the top as you scroll, and opening an issue keeps the period.

At the top, use Open, Resolved and Ignored to switch between issues of each status. Each shows how many issues it has. Sort by orders the list by Last seen, Events or Visitors. Assignee shows the issues of Anyone, those Assigned to me, the Unassigned ones or those of one team member.

The search box finds issues whose message or script contains your text. Type an issue ID, such as IS-2026-001, to find that issue.

Resolve or ignore an issue

Every issue starts as Open. Click the ⋯ menu of an issue, or open it, and choose:

  • Resolve: once you've fixed it. If the error happens again after that, the issue is open again and marked Regressed, so you know the fix didn't work or the error came back.
  • Ignore: for errors you don't plan to fix, such as those caused by browser extensions. An ignored issue stays ignored even when it happens again.
  • Reopen: to make a resolved or ignored issue open again.

To change several issues at once, select them and click Resolve, Ignore or Reopen at the top. These buttons show how many issues are selected.

The status is shared with everyone who has access to the site.

Assign an issue and set its priority

On an issue's page, use the controls at the top right:

  • Assignee: choose the team member who will look into it, or Unassign. You can assign issues to the project's owner and to anyone the project is shared with. An issue stays assigned to someone who leaves the project until you assign it to someone else.
  • Priority: Urgent, High, Medium, Low or No priority. New issues have no priority.

Like the status, the assignee and priority are shared with everyone who has access to the site. Changing them doesn't change the issue's status.

Emails about new issues

When an error happens on your site for the first time, Strabber emails everyone on the project: its owner and everyone it's shared with. The email shows each new issue with its ID, message, script, page and how many times it has happened, with a link to its page. Strabber checks for new issues every few minutes, so several new issues arrive in one email.

Only brand-new issues are emailed. An issue that comes back after you resolved it is marked Regressed in the list, but doesn't send an email.

An issue's page

Click an issue to open its page. Its ID is the page's title. It shows:

  • Events, Visitors, Recordings and Identified users in the period, and how many times it happened in all
  • First seen and Last seen, at any time
  • Details: the full message, the script with its line and column, and the page of the latest event
  • Events per day in the period
  • Where it happens: the browsers, operating systems, devices, countries and pages where it happens most
  • Latest events: the last 10 times it happened, each with a button that plays its recording

Click View recordings to see every recording where the issue happened, or View logs to see each of its log entries. Both open with an Issue filter, which you can combine with other filters.

Good to know

  • Deleting log entries on the Logs and errors page also removes them from their issues. An issue with no entries left disappears. If its error happens again, the issue comes back with the same ID, assignee and priority.
  • Errors are grouped as they're recorded, including errors recorded before issues were available.