Issue Tracking
Group, triage, and resolve errors with automatic issue management.
How issues work
When Moneat receives an error event, it generates a fingerprint and groups the event with other events that share the same fingerprint. This group is called an issue. Each issue tracks occurrences, affected users, first and last seen timestamps, source metadata, and event history.
Issue lifecycle
Issues move through the following states as your team triages and resolves them:
| Status | Description |
|---|---|
| Unresolved | The issue is active and appears in the default issue view. |
| Resolved | The underlying problem has been fixed. If the same error occurs again, the issue can reopen. |
| Ignored | The issue has been intentionally ignored and is excluded from the default active view. |
| Next release | The issue is marked resolved in the next release, so Moneat can close it when a newer release is observed. |
Issue details
Clicking an issue in the dashboard opens the detail view, which includes:
- Stack trace - Full exception stack trace with source context when available
- Breadcrumbs - Timeline of events leading up to the error
- Tags - Filterable metadata such as environment, browser, OS, and source
- User impact - Number of unique users affected
- Event history - Timeline of occurrences with frequency chart
- Device & browser - Client environment information when provided
Filtering & search
The issues list supports filtering options to help you focus on what matters:
- Status - Filter by unresolved, resolved, ignored, or next release
- Service - Show issues from specific services
- Time range - Filter by when issues were first or last seen
- Sort - Sort by last seen, first seen, event count, or user count
Auto-reopening
When you resolve an issue, Moneat continues to monitor for new events matching that fingerprint. If the same error occurs again, the issue is automatically reopened so regressions do not go unnoticed.