Error groups
Errors grouped by cause, with occurrence counts, affected users and the release that introduced them.
Logs & Errors → Error Groups collects individual error events into groups that share a cause.
Grouping
Errors are fingerprinted from the exception type, the message shape and the top of the stack. Ten thousand occurrences of one bug are one group with a count — not ten thousand rows.
What a group tells you
| Occurrences | Total, and over time |
| Affected users / sessions | How many people, not just how many events |
| First seen | Which release it appeared in |
| Last seen | Whether it is still happening |
| Environments | Where |
| Example events | With full stack, breadcrumbs and context |
| Related traces | What the request was doing — see APM |
First seen is the useful field
A group whose first seen is right after a release is a regression, and AccelerUp says so: error groups are correlated with releases, so "what did 4.18.2 break" has an answer without anybody bisecting.
Source maps
Upload source maps to /ingest/sourcemaps and minified stacks resolve to your
source. Without them, every browser error points at main.a8f3c2.js:1:48211.
Upload source maps as part of the build, not by hand. A map that does not match the deployed bundle resolves to the wrong lines, which is worse than not resolving — it sends people to code that is not running.
Status
| Status | Means |
|---|---|
| Unresolved | Still open |
| Resolved | Fixed. Reopens automatically if it occurs again |
| Ignored | Known and accepted; stays out of the default view |
Automatic reopening is what makes "resolved" trustworthy. A fix that did not work does not stay marked as fixed.
Alerting
Rules on:
- a new group appearing
- occurrences exceeding a threshold
- a spike against the recent baseline
- a resolved group reopening
The first and last are the highest-value ones. A brand-new error group in production is nearly always worth a look, and a reopened one means a fix did not hold.
Related
- Network errors — failed requests rather than thrown exceptions
- Patterns — shapes across sources
- Browser SDK — getting front-end errors in
Where this behaviour lives: frontend/src/app/errors/, backend/internal/handler/web_ingest_handler.go. If the code and this page disagree, the code is right — please fix the page.
Part of Logs and errors — What the software said about itself, and what was unusual about it.