Find and triage issues
Search a project's issues with Sentry's syntax, then resolve, ignore, reopen, assign or delete them.
Replace project-id with the project's id and issue-id with an issue's short id (WEB-1A) or
number.
Prerequisites
- To find issues:
errors:ListIssueson the project. Without it, the Issues tab says "You cannot see this project's issues." and an issue's page is not found. - To resolve, ignore, reopen or assign:
errors:UpdateIssueon the project. Without it, an issue's buttons are unavailable with the note "Needs errors:UpdateIssue on this project.", and the Issues tab offers no actions for selected issues. - To delete:
errors:DeleteIssueon the project. - In the console, also
errors:ListProjectson the project to open it, anderrors:GetEventson it to see an issue's event (without it the issue's page says "You can see this issue but not its events."). - To choose an assignee from the organization's people,
iam:ListUserson the service,rn:ews::<organization id>:iam:*; without it the console offers only yourself.
Find issues
The list shows unresolved issues, newest activity first, unless you ask for others. Search takes Sentry's syntax:
| Search | Finds |
|---|---|
is:resolved, is:ignored, is:all |
Issues of that status; without is:, unresolved ones |
level:error |
One level: fatal, error, warning, info, debug |
environment:production |
Issues seen in that environment |
release:1.2.3 |
Issues seen in that release |
assigned:me, assigned:none |
Issues assigned to you, or to nobody |
browser:"Chrome 131" |
Any other tag as key:value; up to five tags |
| free text | Words in the title, the culprit or the location |
- Open the project. The Issues tab lists its issues and refreshes itself.
- (Optional) In the search box, enter a search, such as
level:error release:1.2.3. - (Optional) Under Status, Level or Environment, choose a value. A value chosen here wins over the same key in the search; two or more statuses show issues of every status, and two or more levels or environments leave that filter to the search.
- (Optional) Sort by Events, Users, Last seen or First seen.
With one environment chosen, the list counts that environment alone: an issue's events, users, first and last seen and its 24-hour chart are that environment's, and an issue without events there is not listed. An issue opened from that list keeps the environment. Its latest event, Older / Newer, the tag distribution, the chart and the Events tab show that environment's events, and a note above them gives its numbers. The header still counts every environment.
dcloud errors issues list project-id --query "is:unresolved level:error" --sort events
dcloud errors issues get issue-idGET /errors/api/projects/project-id/issues?query=level:error&sort=events&period=24hThe answer has the issues, the total before paging, and query, the search as it was
understood. period (1h, 24h, 7d, 14d, 30d, 90d) keeps issues seen in that period.
Resolve, ignore, reopen or assign
| Action | What it does |
|---|---|
| Resolve | Closes the issue. Its next event reopens it as regressed, which the default alerts and alert rules can report. |
| Resolve in the next release | Closes it for its latest release: only an event of a newer release reopens it. An issue seen without any release is simply resolved. |
| Ignore | Closes it for a time, until a number of further events, or forever. When the condition passes, its next event reopens it as escalating, which the default alerts and alert rules can report. |
| Reopen | Makes it unresolved again. |
| Assign | Names a person of your organization, or nobody. |
For one issue:
- Open the issue.
- Choose Resolve, or open the menu beside it and choose Resolve in the next release. A closed issue shows Reopen instead.
- Or open Ignore and choose For 1 hour, For 24 hours, For 7 days, Until 100 more events or Forever. An ignored issue does not offer Ignore.
- Or open the assignee list beside them (it shows Unassigned or the person) and choose a person or Unassigned.
For several issues, select them on the Issues tab, then choose Resolve, Resolve in next release, Ignore (forever) or Reopen. The console says how many issues changed.
dcloud errors issues update project-id --ids 74 --action '{"type":"ignore","forMinutes":1440}'PATCH /errors/api/projects/project-id/issues
{ "ids": [74], "action": { "type": "resolve", "inNextRelease": true } }ids are issue numbers (1 to 100 of them), not short ids. action is one of
{ "type": "resolve", "inNextRelease": false }, { "type": "unresolve" },
{ "type": "ignore", "forMinutes": 60, "untilCount": null } (both null ignores forever) and
{ "type": "assign", "iamUserId": null }. The answer is 200 with updated, how many changed;
numbers of another project's issues are skipped.
400 "No such user in this organization" when the assignee is not an IAM user of your
organization.
Delete an issue
The issue and all its events are deleted. If the error happens again, it opens a new issue.
- Open the issue.
- Open the ⋯ menu at the end of the issue's actions and choose Delete issue and events.
Without
errors:DeleteIssueit is unavailable, with the note "Needs errors:DeleteIssue on this project." - Choose Delete.
The console returns to the project's issues.
dcloud errors issues delete project-id --ids 74DELETE /errors/api/projects/project-id/issues
{ "ids": [74] }The answer is 200 with deleted, how many issues went.