1. What is Error Inspector for? #
Analyze web and mobile frontend errors: exceptions, CSP, requests, crashes, ANRs.
The principle #
Error Inspector groups errors from all frontends: request errors, JavaScript exceptions, CSP violations, mobile app crashes and freezes (ANRs). It is part of the new RUM experience.
2. Key features #
What the app offers.
Overview #
| Feature | Role |
|---|---|
| Vue d’ensemble | Errors over time, per frontend, type, OS, browser, app version |
| Explorer | Grouped instances; Edit in notebook, Pin to dashboard |
| Piles lisibles | Upload of source maps or symbol files |
| Tickets | Jira ticket creation with the Jira for Workflows app |
3. Getting started #
First steps.
Step by step #
- Enable RUM for your web and mobile frontends.
- Upload source maps for readable stacks.
- Open Error Inspector and sort by volume.
- Create a ticket from the error.
Prerequisites #
- New RUM experience accepted in Classic or in Experience Vitals.
Source maps. Without them, a minified JavaScript stack is unreadable: add their upload to your build pipeline.
Sources #
From the official documentation consulted in November 2026: labels and availability change with platform versions.
