Skip to content

observe_issues_get

Read one error tracking issue by id, together with the resolved stack of its most recent event.

Tool

observe_issues_get

Read one error tracking issue by id, together with the resolved stack of its most recent event.

Read one error tracking issue by id, together with the resolved stack of its most recent event. Frames with no matching source map are returned unchanged, and an issue whose stack cannot be read still comes back — with a null stack.

Behavior

HTTP
GET /observe/issues/:id

Arguments

NameTypeRequiredDescription
idstringIdentifier of the issue

Response

FieldTypeAlwaysDescription
idstringIdentifier of the issue
stackobjectStack of the most recent event, or null when the issue has no events yet or the stack could not be read
titlestringDisplay title, set when the issue opened and never rewritten
statusstringunresolved, resolved or archived
culpritstringWhere the error appears to come from, or null
servicestringService the most recent event came from, or null if none was reported
assigneestringWho owns the issue, or null if unassigned
lastSeenstringISO 8601 timestamp of the most recent event
firstSeenstringISO 8601 timestamp of the first event
archivedAtstringISO 8601 archive timestamp, or null
eventCountnumberHow many events have landed on this issue
resolvedAtstringISO 8601 resolution timestamp, or null
environmentstringEnvironment the issue was first seen in, or null
fingerprintstringStable grouping hash the issue is keyed on
lastEventIdstringIdentifier of the most recent event that landed on the issue, or null for issues rolled up before this was recorded
lastReleasestringRelease the most recent event was reported from, or null if none was reported
regressedAtstringISO 8601 timestamp of the last regression, or null if it never regressed
groupingRulestringWhich rule of the ladder matched: explicit, stack, exception or message
exceptionTypestringException class of the first event, or null
groupingVersionstringGrouping config version that produced the fingerprint; part of the issue identity

Try it

Read one error tracking issue by id, together with the resolved stack of its most recent event.

When to use

Read one error tracking issue by id, together with the resolved stack of its most recent event. Frames with no matching source map are returned unchanged, and an issue whose stack cannot be read still comes back — with a null stack.

Example

Ask your agent something like this:

Read one error tracking issue by id, together with the resolved stack of its most recent event.

The agent will invoke observe_issues_get with these arguments:

{
  "id": "<id>"
}

Esc

Start typing to search the docs.

navigateselect