The New Relic Browser team is excited to announce the public beta for JavaScript error analytics for Browser Pro users. This new feature brings customers the ability to more accurately troubleshoot JavaScript errors from directly within the Browser UI using error filtering, grouping, and error profiles. You can combine dimensions (browser type, OS version, or device type) with error attributes (error message, app name, or error class) to quickly identify the most problematic errors. By harnessing the power of New Relic Applied Intelligence (NRᴬᴵ), Browser can now also surface the most common groupings of errors, along with relevant details on how frequently each error occurs.

All this means a lot less guesswork! You can now prioritize your error troubleshooting based on the most valuable user impact.

Filtering and grouping the most troublesome JavaScript errors

If you use New Relic Browser to track the customer experience of your applications’ most valuable users, you know how costly JavaScript errors can be.

For example, let’s say that you run an e-commerce site and most of your revenue comes from desktop users who make purchases from the Chrome browser. However, Browser is showing that Chrome users are encountering unusually high error rates, to the extent that some potential customers aren’t able to complete their purchases.

Using JavaScript error analytics, you can filter on key details to narrow down the scope of all types of JavaScript errors.

JavaScript error analytics

[click to enlarge]

These filter and facet capabilities are designed to help you narrow down where an error is occurring most often. By grouping errors across a number of filterable dimensions, you can troubleshoot JavaScript errors faster within Browser’s UI.

Using error profiles for proactive troubleshooting

Often, when you update a site or deploy a new version of a web application, you need to quickly find and fix JavaScript errors.

Error profiles—a subset of the new error analytics feature—leverages NRᴬᴵ to show you the top trends associated with JavaScript errors. Error profiles shows trends for request URI, transaction name, error class, user agent version, error message, user agent OS, device type, user agent name, and more.

Let’s say, for example, you’re a major media company that runs several web properties, and you’re about to roll out a new website for your newest brand. Since this is an important debut, your web team needs to eliminate any JavaScript errors that might detract from the customer experience. Using error profiles, the web team can quickly understand how deep an particular error’s impact is across the site, so they can focus on the most important issues first.

Browser error profiles for JavaScript errors

With error profiles, the web team will be able to determine answers to key questions such as:

  • What percentage of errors come from various browsers?
  • What URLs are experiencing the most errors?
  • What percentage of errors were caused by a third-party app or service?
  • From which device types did most errors occur?

Error profiles use statistical measures to highlight the errors that deviate most dramatically from non-error transactions. They show you where to focus your attention instead of having to manually click through all the dimensions. Stack traces for each error are available, as well as filterable attributes to help narrow down errors by attributes collected.

With this information, web teams teams are now better equipped to troubleshoot the most impacted areas of their applications—in the most efficient ways possible.

Finally, JavaScript errors as events in New Relic Insights

With JavaScript errors stored as events in New Relic Insights, you can now use New Relic Query Language (NRQL) to write real-time queries to reveal JavaScript errors and add error stats to existing Insights dashboards. You can use this functionality to monitor pre- and post-release cycles, or use NRQL data streams to combine JavaScript errors with other sources of data to view on your dashboard.

JavaScript errors in Insights

[click to enlarge]

Join the public beta

With the advent of JavaScript error analytics, Browser Pro users can now isolate and fix the most problematic site errors with more clarity than ever before. To enable this beta functionality, navigate to the JS errors page in New Relic Browser, and click Preview JS Errors Beta.

The JavaScript errors feature is part of our journey toward event-based reporting that gives New Relic Browser customers a more powerful view into their web performance data. The ultimate goal is to provide a rich set of features designed to help you see how page and site performance impacts your business.


Mat Ball is a product marketing manager at New Relic focused on the impact of frontend web applications to business and customer experience outcomes. Previously, Mat worked for SOASTA, where he marketed their data science product. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!