Error Detail

Clicking an error in the browser opens the detail view. This shows the full captured incident, organized into collapsible sections.

Stack trace

The stack trace is displayed with syntax highlighting. Frames that originate from your application code are visually distinguished from frames in node_modules or Node.js internals.

If source maps were resolved at capture time (the default), the stack trace shows your original source file paths and line numbers. The raw unresolved stack is available in a separate toggle if you need to see the compiled output paths.

IO timeline

The IO timeline lists every recorded IO operation from the request that produced the error, in order. Each entry shows:

• the IO type (HTTP, database query, DNS lookup, TCP connection)
• target URL, hostname, or query
• HTTP method and status code (for HTTP events)
• duration in milliseconds, displayed as a visual bar
• whether the operation completed, errored, or was aborted

The timeline is the fastest way to see what your service was doing in the moments before the failure. Look for slow upstream calls, failed database queries, or unexpected ordering.

Request context

If the error occurred inside a request scope, this section shows:

• request method and URL
• request ID
• filtered request headers
• request body (if body capture was enabled)

Process metadata

Runtime information about the Node.js process at the time of capture:

• Node.js and V8 versions
• platform, architecture, and PID
• memory usage (RSS, heap total, heap used, external, array buffers)
• active handles and requests
• event loop lag in milliseconds
• process uptime

This is useful for spotting memory pressure or event loop stalls that may have contributed to the failure.

Environment

The captured environment variables, filtered through the allowlist and blocklist configured in the SDK. Only variables that passed the filter at capture time are shown.

Completeness

The completeness section reports what was and was not captured for this specific incident. Fields include whether request context was available, whether local variables were captured or truncated, how many IO events were dropped, whether PII scrubbing ran, and whether the package was encrypted.

Use this to distinguish "nothing happened" from "something happened but was excluded by policy or by buffer limits."

Raw JSON

The raw JSON section shows the full incident package as serialized JSON. Use this for copying the payload into other tools, sharing with teammates, or inspecting fields that are not surfaced in the other sections.