Find the errors affecting your users.
Errors are grouped by cause, so a spike is one issue with a count rather than a wall of near-identical rows. Each issue opens with its stack trace, the release it first appeared in, the users it reached and the request that produced it.
TimeoutError: pool exhausted after 2000ms
Pool.acquiredb/pool.ts:118createOrderorders/create.ts:44checkoutHandlerhttp/checkout.ts:31processTicksAndRejectionsnode:internal/process/task_queues:95
From a new error to its cause
A new issue carries the release that shipped it and the request that raised it. Here is one error, from the first event to the explanation.
Group, investigate and triage issues
How errors are grouped, what arrives attached to each issue, and how a team keeps the list under control.
Group on frames, exception type and a normalised message, so an id in the text does not split one issue into a thousand.
fingerprintSource maps and debug files applied on ingest, with your own frames separated from library frames.
sourcemapsFirst seen in, last seen in, and a re-opened flag when something you resolved comes back.
releasesDistinct users affected alongside the event count, so you can judge how widely an error has spread.
impactBreadcrumbs, the request, the trace, the surrounding logs and the session replay, on the issue itself.
contextAssign an issue, resolve it in the next release, mute it with an expiry, or mark it as noise.
triagePoint an existing Sentry SDK at Moneat by changing its DSN, keeping your instrumentation as it is.
dsnOpen an issue with its context attached.
Each issue arrives joined to the request that produced it and to the telemetry around that request, so the next step is a click rather than a second search.
- The failing request. Method, route, parameters, headers and the user it belonged to.
- The trace it lived in. One click to the span that was slow in the request that raised this.
- The logs around it. The lines from the same request, already filtered to it.
- The session replay. For browser errors, the recording of what the person was doing.
- First seen
- 14:02:04 · release 2f91c
- Last seen
- 14:19:31
- Users affected
- 311
- Route
- POST /api/checkout
- Frame
- db/pool.ts:88 acquire()
- Trace
- a41f…9c2 · 12 spans
- Assigned
- Priya Raman
Start catching your errors.
Point your SDK at Moneat, upload your source maps, and see grouped issues on your next deploy. Start on the free plan with no card.