observe_issues_resolve

Tool

Mark an issue resolved.

Mark an issue resolved. A later event flips it back to unresolved and emits observe/issue.regressed.

Name	Type	Required	Description
id	string	•	Identifier of the issue

Field	Type	Always	Description
id	string	•	Identifier of the issue
title	string	•	Display title, set when the issue opened and never rewritten
status	string	•	unresolved, resolved or archived
culprit	string	•	Where the error appears to come from, or null
service	string	•	Service the most recent event came from, or null if none was reported
assignee	string	•	Who owns the issue, or null if unassigned
lastSeen	string	•	ISO 8601 timestamp of the most recent event
firstSeen	string	•	ISO 8601 timestamp of the first event
archivedAt	string	•	ISO 8601 archive timestamp, or null
eventCount	number	•	How many events have landed on this issue
resolvedAt	string	•	ISO 8601 resolution timestamp, or null
environment	string	•	Environment the issue was first seen in, or null
fingerprint	string	•	Stable grouping hash the issue is keyed on
lastEventId	string	•	Identifier of the most recent event that landed on the issue, or null for issues rolled up before this was recorded
lastRelease	string	•	Release the most recent event was reported from, or null if none was reported
regressedAt	string	•	ISO 8601 timestamp of the last regression, or null if it never regressed
groupingRule	string	•	Which rule of the ladder matched: explicit, stack, exception or message
exceptionType	string	•	Exception class of the first event, or null
groupingVersion	string	•	Grouping config version that produced the fingerprint; part of the issue identity

Mark an issue resolved.

When to use

Mark an issue resolved. A later event flips it back to unresolved and emits observe/issue.regressed.

Ask your agent something like this:

Mark an issue resolved.

The agent will invoke observe_issues_resolve with these arguments:

{
  "id": "<id>"
}