Issues
How Raccoon groups exceptions and slow executions into issues, and how to triage, assign and resolve them.
An issue is something to fix. Raccoon opens two kinds:
- Exception issues, one for each distinct exception. Every new occurrence of the same exception counts toward the same issue.
- Performance issues, one for each route, job, command or scheduled task that goes over its threshold.
Issues belong to the application, so an exception thrown in both Staging and Production is one issue. Each environment's Issues page lists the issues seen in that environment, and the sidebar badge counts its open ones. Issues are numbered per application, such as #12.
How exceptions are grouped#
- Laravel: the Nightwatch package decides which exceptions are the same, and Raccoon uses its grouping.
- Node.js and OpenTelemetry: the exception's class and the file, line and column it was thrown from.
- Browser: the same, using the original location when a source map is uploaded, so an error keeps its issue across deploys.
A new issue's title is the exception class and its subtitle is the message.
Finding issues#
The list has Exceptions and Performance tabs, and the filters Open, Unassigned, Mine, Resolved and Ignored. Unassigned and Mine only show open issues. Search matches the title or message, or the issue number when you type a number.
For exception issues, Count and Users cover the last 30 days, or 7 days on the Free plan.
Statuses#
| Status | What happens next |
|---|---|
| Open | The issue needs attention. |
| Resolved | The next occurrence reopens it and sends a "reopened" alert. |
| Ignored | Occurrences are still counted, but the issue never reopens and sends no more alerts. |
Change the status from the issue's Status menu:
- Resolve now resolves it right away.
- Resolve on next deploy keeps it open until the environment you choose records a deployment. Use it when the fix is merged but not deployed yet. The issue shows an hourglass until then. Choosing Open again cancels it.
- Ignore closes it for good. Use it for errors you've decided not to fix.
Each change asks for confirmation and can include a comment.
Working on an issue#
- Priority: No priority, Low, Medium or High.
- Assignee: any member of the organization. The assignee gets an email unless they turned it off.
- Description: notes for your team, in Markdown.
- Comments: you can edit or delete your own.
- Activity: every status, priority and assignment change, with who made it. Changes Raccoon made itself, such as resolving on deploy, show as "Raccoon".
The sidebar shows when the issue was first and last seen, the deploys it was first and last reported in, and occurrences per environment for the last 14 days. Copy for AI copies the issue, with its stack trace, as Markdown you can paste into a coding agent. Or let the agent read it directly through the MCP server.
To change many issues at once, select them in the list and use Status, Assign or Priority in the bar that appears. You can change up to 500 at a time.
Related pages#
An exception's page links to its issue. A route, job, command or scheduled task with an open performance issue shows it at the top of its page.