Guide

Errors & Issues

Every error event is grouped into an issue by fingerprint, and issues — not raw events — are what you triage: status, assignee, priority, releases, alerts.

Grouping

The fingerprint folds chained exceptions, collapses recursion, uses in-app frames, and parameterizes messages (ids, emails, URLs → placeholders) so structurally-identical errors group. Override per event with the SDK's fingerprint field, or server-side with fingerprint rules in Project Settings → Filters (match by type/message/path → set a custom group).

Status lifecycle

unresolved → resolved: manually, 'in this release', or 'in the next release'. A recurrence after resolve re-opens the issue as regressed (and can re-alert).
Archive: forever, or until escalating — the issue stays muted until it crosses an event-count or time threshold, then re-opens.
Substatus chips (new / ongoing / regressed / archived) drive the For-Review triage tab.
Priority: an automatic score blends severity, volume and users; override it manually per issue.

Search syntax

is:unresolved level:error environment:production release:web@1.4.2
assigned:me  times_seen:>100  age:-24h  has:release
issue.category:performance   ← only perf issues (N+1, slow query)
free text matches title + culprit

Working the stream

Bulk actions: resolve, archive, assign, merge, delete, mark-reviewed.
Merge folds duplicate issues (counts + users combined); unmerge splits a fingerprint back out.
Similar Issues suggests neighbors by type/culprit.
Seer AI (Settings → Seer AI, bring your own Anthropic key) writes a root-cause analysis + suggested fix per issue.

Ownership rules (Settings → Ownership) auto-assign new issues by path/URL/tag glob — the jentry equivalent of CODEOWNERS routing.

Try jentry free

Hosted error tracking & performance monitoring. Works with your Sentry SDKs — send your first event in minutes.

Get started — free jentry vs Sentry