Read an issue's events
Read an issue's latest event in full, step through its other events, and fetch one event by its id.
An event is kept as the SDK sent it, with its stack trace source-mapped, for the project's retention. Replace issue-id with the issue's short id or number, project-id with the project's id and event-id with an event id (32 hexadecimal characters).
Prerequisites
- Permission for
errors:GetEventson the project. Without it, an issue's page says "You can see this issue but not its events." and its Events tab says "Reading events needs errors:GetEvents on the project." - In the console, also
errors:ListIssueson the project to open an issue (without it the issue is not found).
Read the events
- Open the issue. The Details tab shows its latest event: Event id, Happened, Environment, Release, Transaction, SDK, Trace, Profile and Stored, the Stack trace (the outermost exception first, its frames newest first), Breadcrumbs, Tags, User and the Raw event. Request, Additional data and Attachments appear when the event carries them.
- (Optional) Turn on Only my code to hide library frames.
- (Optional) Choose Oldest, Older, Newer or Latest to step through the issue's events.
- (Optional) Open the Events tab for the issue's latest 500 events, then choose one.
Under Trace, the trace id opens the event's trace when the SDK sent one (see View traces and transactions); under Profile, Flame graph opens the flame graph of the transaction it happened in, when that transaction was profiled.
dcloud errors events latest issue-id
dcloud errors events list issue-id --limit 50
dcloud errors events get project-id event-idGET /errors/api/issues/issue-id/events/latestGET /errors/api/issues/issue-id/events?limit=50GET /errors/api/projects/project-id/events/event-idlatest and get answer row (the event's fields), event (the event as the SDK sent it) and
attachments. list answers the events newest first, without their payload, 25 per page by
default (limit 1–100); pass the last receivedAt as before for the next page. Without
errors:GetEvents each answers 403; an issue or event that does not exist answers 404.
Result
An issue whose events are all past the project's retention says "No stored event for this issue."
In the API, latest then answers 404.