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.

Last updated 18 November 2026View as Markdown

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:GetEvents on 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:ListIssues on the project to open an issue (without it the issue is not found).

Read the events

  1. 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.
  2. (Optional) Turn on Only my code to hide library frames.
  3. (Optional) Choose Oldest, Older, Newer or Latest to step through the issue's events.
  4. (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.

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.

Did this page help you?