docs
Dashboard

Issues & Events

An issue represents a unique error. Individual occurrences of that error are called events. booboo.dev groups events into issues automatically using fingerprinting — errors with the same exception type, normalized message, and top stack frames are grouped together.

Issue grouping

booboo.dev computes a fingerprint for each incoming event based on the exception type, a normalized version of the error message, and the top 5 stack frames. Events with the same fingerprint are grouped into the same issue. If a resolved issue receives a new event, it automatically reopens.

Issue list

The issues page shows all issues for a project. Filter by status using the tabs:

  • Open — active issues that need attention
  • Resolved — issues marked as fixed (they will reopen automatically if the error occurs again)
  • Ignored — issues you've chosen to suppress

Environment filter

If your events include an environment (e.g. "production", "staging"), an environment dropdown appears above the issue list. Select an environment to show only issues that have occurred in that environment. Each issue tracks all environments where it has been seen — so an issue can appear under both production and staging if the error occurs in both.

Issue detail

Click an issue to see its full detail including:

  • Stack trace — the full call stack with source context, separated into app and library frames
  • Event timeline — a list of all occurrences, newest first
  • Status controls — mark as resolved or ignored
  • Environments — badges showing which environments the error has been seen in
  • Metadata — first seen, last seen, total event count

Event detail

Click an individual event to see the complete payload:

  • Stack trace with source context and local variables (Python)
  • Request data — HTTP method and path (when captured by framework integrations)
  • Browser context — URL, user agent, viewport (JavaScript events)
  • Breadcrumbs — trail of actions leading up to the error (JavaScript events)
  • Tags — custom key-value pairs attached by the SDK
  • Environment — the environment the event was captured in