Issues: triage, search, events, grouping and ownership
Every error from a Sentry SDK or a Guidely SDK is grouped into an issue (Monitor → Errors). This page covers what you can do with issues: the list and its search, the issue page and its events, the triage workflow (status, assignee, priority, merge, delete), grouping rules and ownership. Ingest and SDK setup are in ingest.md; alerts in alerts.md.
The issue list
Monitor → Errors, for the environment picked in the header.
- Tabs: Unresolved, For review (new, regressed or escalating), Regressed, Escalating, Ignored, Resolved, All.
?status=alletc. in the URL still work. - Each row: a colour bar for the level (fatal, error, warning, info, debug), the title (type) and message, the short id (
NORTHWIND-42: the project slug and a per-project number), level, priority, badges (New, Regressed, Escalating, how it is ignored or resolved), bookmark, culprit (file:function), last seen and age, a trend sparkline, events and users in the period and the assignee (click it to assign). - Sort: last seen, first seen, most events, most users, priority.
- Filters: search (below), category (error, performance, uptime, cron, feedback), app version / release, and the environment in the header.
- Bulk actions (select rows): resolve (now, in the next release, in the current release, in a release you name), ignore (with any condition below), unresolve, assign, priority, merge, bookmark, delete (optionally discard).
- Keyboard:
/focuses the search,j/kmove,xselects,Enteropens. - Saved searches: the Searches menu has recommended searches (assigned to me, my bookmarks, unassigned high priority, new today, unhandled), the project's shared searches and your own. "Save current search" keeps the query and sort; sharing with the project needs "Manage insights & alerts".
Search syntax
Type key:value filters and free text; everything is ANDed. Autocomplete offers keys (including every tag key seen in the last 30 days) and then values.
| Filter | Meaning |
|---|---|
is:unresolved is:resolved is:ignored (is:archived) | Status (overrides the tab) |
is:assigned is:unassigned is:bookmarked is:subscribed | Triage state of the issue / for you |
is:new is:ongoing is:regressed is:escalating is:for_review | Substatus |
is:linked is:unlinked | Has a ticket (Jira, Linear, GitHub…) |
ticket.state:open ticket.state:done ticket.state:canceled ticket.state:closed | A linked ticket's state in its tracker: still open, closed as done, closed without a fix (won't do, duplicate, not planned), either closed |
ticket:ENG-123 ticket:web#12 ticket:any ticket:none (ticket.key:) | A linked ticket by key (* wildcard) |
ticket.provider:linear (tracker:) | Tracker a linked ticket is in |
assigned:me assigned:ada@acme.com assigned:none | Assignee |
assigned_or_suggested:me | Assigned to you, or unassigned and you're a suggested owner |
bookmarks:me subscribed:me | Bookmarked by / participant |
level:error level:[error,fatal] | Level |
issue.priority:high (priority:) issue.category:error (category:) | Priority, category |
first-seen:-24h last-seen:+7d age:-1h first-seen:>2026-01-01 | Dates: -24h = within the last 24 hours, +7d = more than 7 days ago; units s, m, h, d, w |
times-seen:>10 times-seen:<=1k | All-time events |
release:1.2.0 release:latest | Had events in that release (counts and trends cover only them) |
firstRelease:1.2.0 | First seen in that release |
error.type:TypeError error.value:"timed out" culprit:checkout platform:python | Issue fields (* wildcard; value matches contain) |
error.handled:false error.unhandled:true error.mechanism:onerror | Handled or not, capture mechanism |
environment:prod browser.name:Chrome os.name:iOS device:iPhone15,2 url:*/checkout* transaction:/cart server_name:web-1 runtime:"node v22" | Tags (below) |
user.email:ada@acme.com user.id:42 user:"id:42" | Users |
area:billing tags[area]:billing | Any custom tag |
has:user !has:release | Has a value for a tag |
!key:value | Negates any filter |
NORTHWIND-42 | Short id (also a merged issue's old short id); Enter jumps straight to it |
| a 32-character event id | Enter opens that event |
Unknown keys search the tag of that name, as in Sentry. Filters Guidely can't apply are listed under the search box. Tag filters look at events within the list's date range.
The Tickets picker next to the categories applies the common ticket filters (has a ticket, ticket open, ticket done, ticket closed without a fix, no ticket). Each row shows its linked tickets' keys, ticked when the ticket is done.
Linked tickets resolve their issues
When a ticket opened from (or linked to) an error is closed as done in Linear (a completed state), Jira (Done status category, unless its resolution is Won't Do, Duplicate, Cannot Reproduce and the like) or GitHub (closed as completed), Guidely resolves the error:
- in the next release when the project reports releases: the error counts as fixed from the build that ships the fix. Events from the release that was current when the ticket closed (and older ones) don't reopen it; an event in a newer release regresses it as usual. The issue shows Resolved after 1.4.2.
- at once when the project reports no releases.
Not while another ticket linked to the same error is still open, and never for tickets closed without a fix. Reopening the ticket (or changing it to won't do) reopens the error, unless someone changed the error's status since. The activity says which ticket did it. A commit that says Fixes ENG-123 (the ticket's key) resolves the error in the exact release that ships it (releases).
GitHub (with the GitHub App) reports closes and reopens at once; every tracker is also checked every ~10 minutes (the tickets.sync job, error tickets only, Linear and Jira 50 tickets per request). Tickets linked before this existed are only recorded on their first check, never resolved from it. Turn it off per tracker: Settings → Issue trackers → Resolve errors when done (PATCH /ticket-integrations/:id { autoResolve: false }).
The issue page
/app/<project>/errors/<issue>. The header shows the title, message, culprit, short id, level, platform and counts, with the triage actions: Resolve (split button), Ignore (split button), Assign (suggested owners first), Priority, Bookmark, Subscribe (the bell), Watch replay, Create ticket and, under ⋯, all replays of the issue and Delete.
Tabs:
- Details: the latest event in full, and the sidebar (events chart, details with first / last release, suggested assignees, tag distribution, participants, alert coverage, pages, app versions).
- Events: every event, newest first, searchable with the event filters (
release:,user.email:,user.id:,url:,browser:,os:,level:,environment:,transaction:,error.handled:, any tag,has:, free text or an event id). - Tags: every tag key with its top values and share; each key has its own page with every value, count, share and first / last seen, and a search link.
- Activity: comments and history.
- Merged: fingerprints merged into the issue, and unmerge.
Events
Each event has its own URL: /app/<project>/errors/<issue>/events/<event id> (also latest and oldest). /app/<project>/errors/events/<event id> finds the issue an event belongs to, and /app/<project>/errors/by-short-id/NORTHWIND-42 finds an issue by short id. Navigation buttons go to the oldest, older, newer and newest event; JSON opens the stored payload.
For Sentry SDK events the page shows everything the SDK sent:
- Highlights: level, handled, release, environment, dist, user, transaction or URL, browser and OS, server, platform, trace (links to the trace view).
- Exception: the whole chain (the main exception first, then what caused it), each with handled / unhandled, mechanism, synthetic and exception-group badges and mechanism data, and its stack trace. Switch between App frames (system frames collapsed) and Full stack, newest or oldest call first, or Raw (as the SDK would print it). A frame expands to its code context (from the SDK, or from an uploaded source map for JavaScript) and local variables.
- Threads: pick a thread (crashed / current marked) to see its stack.
- Breadcrumbs: a timeline with an icon per type (navigation, http, click, input, console, query, error…), level, time relative to the error and data; filter by type and level, search. The last 10 show first.
- Tags: each tag links to a search for issues with it.
- Contexts: browser, OS, device, runtime, app, trace (with Open trace), and any other context.
- HTTP request: method, URL, query, body, headers (cookies and credentials are never stored) and environment.
- User, Additional data (
extra), SDK and packages (SDK name, version, integrations, packages and installed modules) and the SDK's fingerprint.
Guidely SDK events have no full payload: they show the stack trace (source-mapped when maps are uploaded) with the occurrence's user, browser, URL and replay link, as before.
Tags
Every event's tags are counted per issue and day (the tag store): level, handled, mechanism, environment (as the SDK sent it), release, dist, browser, browser.name, os, os.name, device, device.family, runtime, runtime.name, url, transaction, server_name, logger, user (id:42, else email:, username: or ip:), user.id, user.email, user.username, and every custom tag (the SDK's own tags win over derived ones of the same name). Guidely SDK exceptions get level, handled, mechanism, environment, release, url, browser, os, device, user and platform. Tag counts expire with the events.
Workflow
Status
| Status | Substatus | Notes |
|---|---|---|
| Unresolved | New | First seen within 7 days |
| Ongoing | ||
| Regressed | Was resolved, happened again (for 7 days) | |
| Escalating | An ignore condition was met, or it spiked while ignored (for 7 days) | |
| Ignored | Forever | |
| Until escalating | Reopens as Escalating when the last hour has 3× its hourly average over the week before ignoring, and at least 10 events | |
| Until a condition | For N minutes; until it happens N more times (optionally within a window); until it affects N more users | |
| Resolved | Now, in the next release, or in a release |
- Resolve reopens on any later event (a regression).
- Resolve in the next release: the fix ships in the release after the current one. Events in the current release (the issue's app's latest release when it was resolved) or older don't reopen it; events in a newer release do.
- Resolve in release X: events in X or an older release don't reopen it; newer ones do. Events without a release always reopen it.
- Releases compare by number when they're dotted versions of the same package (
1.2.10>1.2.9,api@2.0.0>api@1.9.0, avprefix ignored); otherwise by when the project first saw them. - The
errors.workflowjob (every 2 minutes) reopens ignored issues whose condition is met.
Priority
High, medium or low. New issues get it from their level and whether they were handled: fatal and unhandled errors are high, handled errors medium, warnings, info and debug low. An issue seen 100 or more times in an hour becomes high. Once someone sets the priority it stays as they set it.
Assignment, participants and emails
Assign to any member of the workspace (teams: see Ownership below). Teammates become participants when they're assigned, comment, are @mentioned or subscribe with the bell; unsubscribing sticks. Participants get an email (sent through the outbox; in HIPAA workspaces only a generic notice) when the issue is assigned, commented on or regresses; @mentioned teammates get a mention email. Nobody is emailed about their own actions.
Comments and activity
Comments support @mentions: type @ and pick a teammate (@Ada Lovelace or @ada@acme.com). Authors (and admins) can edit or delete comments. The activity log records first seen, first release, regressions, status changes (with release and ignore details), automatic reopening, escalation, assignment (including by ownership rules), priority changes, merges and unmerges.
Merge and unmerge
Select issues of one environment and Merge: the issue with the most events becomes the primary, and the others' events, comments, activity, participants, bookmarks, alert history, ticket links and replay alert rules move to it. Their fingerprints keep pointing at the primary, so their future events land in it too, and their old short ids still find it. Merged → Unmerge gives a fingerprint its own issue back, with the same id and short id and the events counted since.
Delete and discard
Delete removes the issue with its events, payloads and tags; the next event like it opens a new issue. Delete and discard also drops its future events at ingest: they are not stored or counted against your allowance. Issue settings → Discarded lists them, and Undiscard accepts them again.
Grouping rules
Issue settings → Grouping (admins). Rules apply to new events only; Test on recent issues re-groups the latest event of the 50 most recently seen issues with the rules you're editing and shows which rules matched and which issues would merge.
Fingerprint rules, one per line: matchers -> fingerprint parts.
error.type:ChunkLoadError -> chunk-load-error
message:"timeout*" -> timeouts, {{ transaction }}
tags.area:billing !level:warning -> {{ default }}, billing title="Billing: {{ error.type }}"
- Matchers (all must match):
error.type(type),error.value(value),message,logger,level,platform,release,transaction,sdk,tags.<key>, and frame matchers that match when any frame matches:path(stack.abs_path),module,function,package,app(yes/no).!negates a matcher. - Parts: text,
{{ default }}(Guidely's own grouping),{{ error.type }},{{ error.value }},{{ message }},{{ function }},{{ module }},{{ path }},{{ package }},{{ level }},{{ logger }},{{ transaction }},{{ release }},{{ tags.<key> }}. Frame variables use the frame that matched (else the innermost in-app frame). title="…"names the issue (the event keeps its own type).- The first matching rule wins.
Stack trace rules, one per line: matchers actions.
path:**/node_modules/** -app
function:assert* -group
module:com.acme.* +app
- Actions:
+app/-appmark frames as your code or not (this also moves the culprit and the in-app frames shown on the issue page),+group/-groupuse or skip frames for grouping. - Every matching rule applies, in order; later rules override earlier ones.
Matching ignores case. * matches anything, except in paths, where * stays within one folder and ** crosses folders; a relative path (src/billing/*) matches at any folder. Values may be quoted.
Precedence: a matching fingerprint rule beats the SDK's fingerprint; the SDK's fingerprint beats Guidely's default grouping; stack trace rules shape the default grouping (and {{ default }}). For source-mapped JavaScript, the default grouping uses the original source of the innermost in-app frame as the SDK marked it.
Ownership
Issue settings → Ownership ("Manage insights & alerts").
Ownership rules, one per line: type:pattern owner [owner…].
path:src/billing/* billing-lead@acme.com
url:*/checkout/* #payments
tags.area:search @ada-gh
module:com.acme.sync.* grace@acme.com
- Types:
path(any frame's file),module(any frame's module),url(the request or page URL),tags.<key>(a tag value).*matches anything here,/included. - Owners: a member's email,
@github-login(members who sign in with GitHub), or a team-like handle (#payments,@acme/billing) listed in the mapping.
CODEOWNERS: paste your repository's file. Patterns match frame paths at any folder, since Guidely doesn't know where your repository root is in a stack trace (/src/billing/ matches /srv/app/src/billing/charge.py).
Team and handle mapping: @acme/billing = ada@acme.com, grace@acme.com, one per line. Guidely has no teams of its own, so this is how #team owners resolve to members.
The owners of every matching line are suggested on the issue page, the last matching line first, ownership rules before CODEOWNERS; in-app frames are tried first. With Auto-assign on (the default), a new issue is assigned to its first suggested owner, who becomes a participant and gets an email. Test on recent issues shows who the rules you're editing would suggest.
API
Dashboard API (session or MCP auth), all under /api/v1:
| Route | ||
|---|---|---|
GET /projects/:id/errors?query=&status=&sort=&q=&appVersion=&userId=&page= | List (query is the search syntax) | |
GET/PATCH/DELETE /errors/:id | Issue; PATCH { status, statusDetails: { inNextRelease, inRelease, ignoreDuration, ignoreCount, ignoreWindow, ignoreUserCount, untilEscalating }, assigneeId, priority, bookmarked, subscribed }; DELETE ?discard=1 | |
POST /projects/:id/errors/bulk | { ids, action: resolve·unresolve·ignore·assign·priority·merge·delete·discard·bookmark·unbookmark, … } | |
POST /projects/:id/errors/merge, POST /errors/:id/unmerge, GET /errors/:id/merged | Merge | |
GET /errors/:id/events, GET /errors/:id/events/:eventId (latest, oldest), GET …/json | Events | |
GET /errors/:id/tags, GET /errors/:id/tags/:key | Tags of an issue | |
GET /errors/:id/activity, POST /errors/:id/comments, PATCH/DELETE /error-comments/:id | Activity, comments | |
| `GET /projects/:id/errors/lookup?shortId= | eventId=` | Find an issue |
GET /projects/:id/errors/tags, GET /projects/:id/errors/tags/:key?prefix= | Autocomplete | |
GET/POST /projects/:id/errors/saved-searches, DELETE /error-saved-searches/:id | Saved searches | |
GET/PUT /projects/:id/errors/config, POST /projects/:id/errors/config/preview | Grouping and ownership | |
GET /projects/:id/errors/discards, DELETE /error-discards/:id | Discards | |
GET /projects/:id/errors/assignees | Members who can be assigned |
Code map
apps/web/src/lib/issue-search.ts: the search syntax (shared with the search bar).apps/web/src/server/services/:errors.ts(list, issue, lookup),error-search.ts(search → SQL),error-events.ts,error-tags.ts(tag store),error-workflow.ts(status, release gating, merge, delete / discard, bulk, ingest hooks, theerrors.workflowjob),error-issue-comments.ts(comments, activity, saved searches, tag pages),error-issue-notify.ts(activity log, participants, emails),error-issue-fingerprints.ts(merged fingerprints, discards),error-grouping-rules.ts/error-grouping.ts(rules, settings, preview),error-ownership.ts.- Ingest hooks:
services/sdk.ts(grouping rules intoprepareException, discards, merged fingerprints and release gating inupsertErrorIssues,afterErrorIngest) andsentry/handlers/event.ts(grouping input,afterSentryEvent). - Models:
ErrorIssue(substatus, priority, assignee, ignore and release fields, first / last release, suggested owners),ErrorIssueFingerprint,ErrorDiscard,ErrorTagValue,ErrorIssueComment,ErrorIssueActivity,ErrorIssueSubscription,ErrorIssueBookmark,ErrorSavedSearch,ErrorIssueConfig.