Monitor browser errors
JavaScript error aggregation
Splunk RUM's APPLICATION SUMMARY DASHBOARD displays JavaScript errors (grouped by error ID) which occur most often in your applications. The error ID is created by hashing the associated stack trace, error message, and error type. When you drill into an error, you can see the error type, the error message, associated stack trace, and the trend of the error frequency. For more information about the error ID, see About the error ID.
To see errors from a specific browser application:
Scroll down to the application name and expand its section. The expanded section displays a JavaScript Errors pane on the right.
To see details about a specific error, select it.
If Splunk RUM has source mapping for this application, it displays the error's stack trace in readable form. Otherwise, it displays a message indicating that it didn't detect any source mapping that corresponds to this error.
Find the top JavaScript errors across your applications
In Splunk RUM, the JavaScript errors view shows the JavaScript errors sorted by page, whereas the metric JavaScript Errors (by error ID) shows the top ten JavaScript errors across your entire application. In the metric Frontend Errors by ErrorID the information is displayed by error type, error ID, then error message.
Open RUM.
From the left navigation panel, select RUM and Browser as the source and the application you wan to monitor.
To open Tag Spotlight from either the APPLICATION SUMMARY DASHBOARD or Overview, click any metric.
For example, select See all in the metric JavaScript errors(by error ID) to explore all of the JavaScript errors in Tag Spotlight.
Troubleshoot JavaScript errors without stack trace, type, or message
Sometimes, you might see a message in the UI that says JavaScript error without a stack trace, type, or message. This might happen because the error didn’t have any information about the stack trace before it was ingested by Splunk RUM. To troubleshoot, try narrowing in on a specific time range which shows the JavaScript error only, and explore the related user sessions.
Upload source maps for readable stack traces
The information in most raw stack traces is not fully human readable. To make your raw stack traces easier for you to read, you need to provide source maps that correspond to this browser application. Source maps enable Splunk RUM to translate raw stack traces back into a human-readable form. You can either upload source maps now ("on-demand") or as part of your application's CI pipeline:
To upload source maps now, select Upload on this dashboard.
To upload source maps as part of your application's CI pipeline, see Set up JavaScript source mapping.