observe_issues_event

Tool

observe_issues_event

Read one event of an error tracking issue in full — the most recent one by default, or a specific one by id.

Read one event of an error tracking issue in full — the most recent one by default, or a specific one by id. Returns where and in what it happened: service, environment, release, trace, tags, and for OTel events the span with its HTTP method, route, status and target address. An issue whose events are no longer stored still comes back, with a null event.

Behavior

HTTP: GET /observe/issues/:id/event

Arguments

Name	Type	Required	Description
id	string	•	Identifier of the issue
eventId	string	—	Which event to read; omit to read the most recent one. Must be an event of this issue

Response

Field	Type	Always	Description
event	object	•	The event, or null when the issue has no event id or the event is no longer stored — events live 30 days and an issue outlives them. Neither case is an error
source	string	•	Which store the event id addresses, derived from its shape. Null when there is no event id
eventId	string	•	Identifier of the event that was read, or null when the issue has recorded no event id yet
issueId	string	•	Identifier of the issue the event belongs to

Try it

Read one event of an error tracking issue in full — the most recent one by default, or a specific one by id.

When to use

Example

Ask your agent something like this:

Read one event of an error tracking issue in full — the most recent one by default, or a specific one by id.

The agent will invoke observe_issues_event with these arguments:

{
  "id": "<id>"
}