Last updated: March 14, 2026
Monitor JavaScript Errors
The JavaScript Errors built-in view filters the event stream to browser.error events. These are unhandled JavaScript exceptions and unhandled promise rejections captured automatically by the Web SDK — no manual instrumentation required.
The chart shows error frequency over the selected time window. Sparse, irregular spikes typically indicate intermittent issues (race conditions, flaky APIs). A sustained baseline of errors appearing at regular intervals often points to a reproducible bug tied to a specific user action or page.
Use the Error Table
The JavaScript Errors table surfaces the columns most useful for triage:
| Column | Description |
|---|---|
| Time | When the error was thrown |
| Website | Which instrumented site the error came from |
| Exception type | The JavaScript error class (e.g. TypeError, RangeError) |
| Exception message | The full error message string |
| URL path | The page the user was on when the error occurred |
A repeated exception message across multiple rows is a strong signal of a systematic bug rather than a one-off user issue.
Use the Groups Tab
Switch to the Groups tab to aggregate errors by exception.message or url.path.
This immediately shows you which errors are most frequent and on which pages they concentrate — making it straightforward to prioritise what to fix first.
Use the Event Sidebar
Click any row to open the Event Sidebar.
In addition to the standard session context (user, device, location), the Body field contains the raw error payload.
The Attributes section includes metadata such as the Kubernetes component that served the page and the page load ID, which you can use to correlate the error with a specific page load event.
The Session section in the Event Sidebar shows which user encountered the error. Click View full session to open the full session replay in Websites and see exactly what the user was doing — including prior page views and HTTP requests — in the moments before the error was thrown.