Error Report Structure

An individual error report page in Telebugs is divided into sections that provide layered context about the error.

Use P and N to open the previous or next occurrence in the active ordering. If you opened a report from a filtered error-group Reports list, that ordering includes the full filtered result. Navigation stops at either boundary.

Use U to return to the originating list. Same-tab navigation restores its URL, filters, pagination, scroll position, and any visible keyboard cursor. Direct, shared, and new-tab reports fall back to the error group’s Reports list.

The error-group header also provides R to resolve or unresolve, M to mute or unmute, and A to claim or unclaim the error for yourself. These actions work on the Details, Reports, and Notes tabs.

The same available occurrence and error actions appear in the command palette, which opens with Command-K or Control-K.

See Accessibility for the complete context-aware shortcut reference and safety behavior.

Report Details

High-level overview:

Error message: The main description of what went wrong.
When: Relative time (e.g., “5 minutes ago”).
Occurred at: Exact timestamp in the project’s timezone.
Handled: Whether the error was caught and reported manually or unhandled.
Severity: Level such as error, warning, or info.
Server name: Host where the error occurred.
Environment: Production, staging, etc.

Backtrace

The stack trace showing where the error originated.

Each frame lists:

Filename
Function/method name
Line (and column) number

Code context is shown around the error line (highlighted). Frames can be expanded for more lines.

If source maps are attached to the release, minified traces resolve to original source files.

Quick tip: Focus on “in-app” frames (your code) and ignore library frames when investigating.

HTTP Request

For web-related errors, details of the triggering request:

Method and full URL
Headers
Environment variables (e.g., remote IP)
Body data (form fields, JSON, etc.)

Useful for reproducing API or page errors.

Breadcrumbs

A timeline of events leading up to the error (console logs, navigation, HTTP calls, etc.).

Each breadcrumb shows timestamp, category, message, and data. Expand for full details.

Enable automatic breadcrumbs in your SDK for richer trails.

Contexts

Environmental details:

OS name and version
Runtime (e.g., Node.js, Python)
Device or browser info

Helps identify platform-specific issues.

Dependencies

List of loaded packages/modules with versions (e.g., express: 4.18.2).

Check here for known vulnerable or incompatible versions.

SDK

Shows which Sentry SDK sent the report and its version.

Affected User

User information (if set via SDK):

ID, username, email
IP address and approximate geo location

Set with Telebugs.setUser({ id: '123', email: '[email protected]' }).

Additional Data

Custom key-value data sent with the report.

Use for anything not covered elsewhere.

Ingestion Warning

If an incoming event contains more collection entries or longer strings than Telebugs can safely retain, the report shows an Ingestion warning above its details. The error was accepted and grouped normally; only some diagnostic detail was shortened or left out.

The warning identifies affected sections and shows how many entries were omitted or strings were shortened. Repeated oversized events are normalized deterministically, so grouping remains stable.

See Ingestion and Upload Limits for the exact collection limits and suggestions for reducing noisy SDK data.

Viewing Raw Data (View as)

On any individual error report page, you can access alternative representations of the report data using the View as dropdown.

Available formats:

Structured (default)

The standard Telebugs interface with organized sections (Backtrace, Request, Tags, etc.).
JSON

The stored event payload as pretty-printed JSON. Useful for copying data, debugging SDK integration, or programmatic processing. When event details were shortened, the summary is available at details.ingest_truncations.
XML

The event payload rendered in XML format (for compatibility with certain tools or legacy systems). Ingestion changes appear in <ingest_truncations>.
Markdown

A clean, human-readable Markdown summary of the report, including the error message, formatted stack trace (in code blocks), key contexts, tags, and other details. Ideal for pasting into tickets, pull requests, or chat. Ingestion changes appear in an Ingestion warning section.

Selecting a format instantly opens it in the same tab at a new URL, for example:

https://your-instance.example.com/errors/2003/reports/982768.json
https://your-instance.example.com/errors/2003/reports/982768.xml
https://your-instance.example.com/errors/2003/reports/982768.markdown

These URLs can be shared directly — anyone with access to the project will see the report in the chosen format.

Tip: Bookmark or share the direct .json, .xml, or .markdown URL when you need to reference the raw or formatted version outside of Telebugs.

The Telebugs Manual