Issues
Errors & feedback → Errors lists every issue your site has had. An issue groups all the errors that are really the same problem, so a thousand failed loads of one chunk are one row. The tab shows how many issues are open, such as Errors 12. An issue people wrote about through the feedback widget shows a speech bubble with how many notes it has.
How errors become issues
SnowAnalytics gives each error a fingerprint and groups errors with the same one:
- Browser errors: the type, the message with numbers, ids, quoted values and URLs replaced, and the top frame from your own code.
- Failed loads: the asset's path with its hash removed.
- Network errors: the method, the path with ids turned into
:id, and whether it was a 5xx or a failure. - Console errors: the normalized message.
- Server errors: the type, the normalized message and the top frame from your project.
Merged issues show under the one they were merged into.
States
Each issue has one state, the first that fits:
| State | Meaning |
|---|---|
| Resolved | You resolved it and nothing has happened since. |
| Regressed | You resolved it and it came back. |
| Ignored | You muted it. |
| New | First seen in the last 7 days. |
| Escalating | In the last 24 hours it has at least 5 events and at least twice its daily average of the week before. |
| Ongoing | Anything else. |
Five tabs cut the list, each with a count and a note: Unresolved (everything open: regressed, new, escalating and ongoing), New, Regressed, Ignored and Resolved.
The list
Each row shows the error's type and message, where it happened, its events, the people hit, the revenue at risk, a 24-hour trend, when it was first and last seen, and who owns it. Open a row for the issue in full. Seven issues show to a page.
- Search messages, files, pages finds issues by their text.
- Filter, at the top of the page, narrows the list by Env, Release and Assigned (which includes Unassigned), and by the visitor filters every page has, such as Browser and Country.
- Sort orders by Revenue at risk (the default), People, Events, Last seen or First seen.
Under the list, a note says how many errors were filtered as noise and why, such as 8.4k filtered for you.
Ignore errors like this
Some errors repeat with a different address each time, such as Failed to load script for every blocked ad tag. Ignoring them one issue at a time doesn't keep up. On an issue's page, open Ignore and choose Every error like this…. The box starts with the message up to its first address. Edit it if you like, then choose Ignore.
- Every issue the phrase already matches is ignored at once.
- From then on, matching errors are filtered as noise, under Your ignore rules. They are kept, not counted. A new rule takes up to a minute to apply.
- The phrase matches anywhere in the message, in any case.
The same dialog lists the site's rules, with Remove on each. Your ignore rules in the noise note under the list opens it too. Removing a rule makes new errors count again. The issues it ignored stay ignored until you reopen them.
To stop these errors in the browser instead, so they are never sent, use data-ignore-errors.
Act on several at once
Tick rows and a bar offers the actions that fit the tab:
- Resolve, which marks the issue fixed. On an issue's own page with a release, Resolve in next release replaces it, so the issue only comes back if a newer release reports it again.
- Ignore, which mutes it. Its events are kept, not deleted.
- Reopen, which puts a resolved or ignored issue back.
- Assign, to a person who can open the site.
- Merge, which folds the ticked issues into the first one in the table. Their events count as one issue from then on, and it can't be undone.
Viewers can read issues but can't change them. The demo is read-only.
Releases
Under the list, the Release health section shows how your newest release went against the ones before it. It needs release names, and until a release reports, it says so.
- Latest release names the newest build and when it shipped. Visits with an error is the share of that release's visits that hit an error, with how it compares to the release before. A bar for each recent release lets you see a bad deploy at a glance, and badges count its new issues and regressions.
- Releases lists the last 60 days of builds, newest first, six to a view. View all shows the rest. Each row has when it shipped, the share of its visits that met an error, its new issues, its regressions, the people hit and the revenue at risk. With GitHub connected, each release also shows the pull request it is known by. A release counts from its first deploy, error or reported page view.
- Source maps lists the newest releases as Uploaded or Missing, with a Copy upload command button. A missing map means that release's stack traces stay minified. See Source maps.
- Suspect change appears only when GitHub is connected and one of the release's pull requests changed the file one of its new issues fails in. It names the pull request, its author and the file, with Open pull request and See the issue.