Error Groups

How errors are grouped, prioritized, and managed.

Automatic Grouping#

JustAnalytics automatically groups similar errors together using a fingerprinting algorithm based on:

  1. Error type (TypeError, ReferenceError, etc.)
  2. Error message (normalized to remove variable data)
  3. Stack trace (top frames, normalized paths)
  4. Environment (production, staging, etc.)

This means you see one entry for "Cannot read property 'name' of null" instead of thousands of duplicate entries.

Error Group Detail#

Each error group shows:

  • Total occurrences and frequency chart
  • Affected users count
  • First and last seen timestamps
  • Stack trace with source context
  • Browser/OS breakdown of affected users
  • Related session replays

Status Management#

Error groups can be in one of these states:

| Status | Description | |--------|-------------| | Unresolved | New or recurring error (default) | | In Progress | Someone is investigating | | Resolved | Fixed -- will reopen if error recurs | | Ignored | Will not trigger alerts or appear in default views |

Custom Fingerprinting#

Override the automatic grouping by providing a custom fingerprint:

JA.captureException(error, {
  fingerprint: ['payment-gateway', error.code],
});

This groups all errors with the same gateway error code together regardless of stack trace differences.

Use the error explorer to filter errors by:

  • Status -- unresolved, resolved, ignored
  • Level -- error, warning, fatal
  • Browser -- Chrome, Firefox, Safari, etc.
  • OS -- Windows, macOS, iOS, Android
  • Release -- filter by application version
  • Environment -- production, staging, development
  • Date range -- custom time windows

Notifications#

Configure alerts when error groups meet certain criteria:

  • New error group seen for the first time
  • Error rate exceeds a threshold (e.g., >100 per minute)
  • Error affects more than N unique users
  • Resolved error has regressed (recurred)