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

Name
Type
Required
Description
id
string
•
Identifier of the issue

Response

Field
Type
Always
Description
id
string
•
Identifier of the issue
stack
object
•
Stack of the most recent event, or null when the issue has no events yet or the stack could not be read
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

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.

↑↓navigate↵select