Issues

What an issue is

An issue is events that share an error fingerprint. The title is the error. The page shows a sample event, how many people were affected, and when it was first and last seen.

If nobody was identified when it happened, the people list says so. Call identify() on a web request, or forPerson() inside background work, and later events on that issue can name them. A named job still links the issue to that run when no person was set.

Work an issue

Filter the list, open the issue, and read the sample. The sessions on the right are the visits that hit it. Open one to see the timeline around the error.

Mark resolved when you have shipped a fix. Reopen puts it back. Ignore drops it out of the open list. If it returns after you resolved it, the status becomes regressed.

Run investigation on the issue explains the group, not one visit. The same button on a session explains that visit.