- Go to one.newrelic.com > Browser > (select an app) > JS errors.
- Use the available options in the UI to examine what may be causing the errors.
- Optional: Review event logs or stack traces in the UI.
- Optional: Query and create dashboards for JS error data with the query builder, or use the API to monitor or log errors.
Available options in the UI include:
If you want to...
Search through long error lists
Use the Search box so you can more quickly find and fix errors by keywords, URLs, etc.
Group and filter attributes
See notable anomalies and patterns
The Error profiles table shows notable statistical variations, such as browser versions or devices that have errors occurring more frequently than normal.
Examine error details
Examine events leading up to error
The Event log shows the browser interactions, AJAX calls, and traces that led up to an error.
one.newrelic.com > Browser > (select an app) > JS errors: Use this page to group and filter errors, explore stack trace details, and examine trends. (If your UI page looks different, you may be using an older, deprecated UI.)
New Relic saves JS errors as event data. This allows you to query your error data in the query builder. To run NRQL queries and create dashboards to view or share, query the
To notice or log your app's handled errors or other miscellaneous errors, use the Browser monitoring API's
SPA monitoring must be enabled.
The event log shows the browser interactions, AJAX calls, and traces that led up to a JS error. This can help you troubleshoot the root cause of errors.
To view the Event log (if available): Go to one.newrelic.com > Browser > (select an app) > JS errors > (select an error) > Error instances. The event log will not be visible if there are no events in the event log.
For example, if a JS error is occurring after an AJAX request that provides an error message, it could be that your AJAX request doesn't contain the right information. This results in a JS error due to a failed AJAX call.
Stack traces can show you if an error is breaking important functionality, or if it's a less important error. To view an error's stack trace (if available): go to one.newrelic.com > Browser > (select an app) > JS errors > (select an error) > Error instances.
For some older browsers, the following errors may be unavailable:
Script error: These occur while the script is loading, so they do not produce a stack trace.
- Errors thrown from third-party scripts that reside on another domain are not available.
- Errors occurring on older browsers: These may not be able to provide a usable stack trace. In some cases, they may not provide a stack trace at all.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.