Compatibility and requirements for New Relic Browser

New Relic Browser is a robust, standalone product with browser monitoring features that enhance (but do not require) New Relic APM. Before you install New Relic Browser or enable the enhanced features, make sure your system meets these requirements.

For browsers that support the New Relic UI and other New Relic products, see Supported browsers for New Relic's UI.

Basic requirements

To report data to New Relic Browser, your application must at a minimum meet two basic requirements:

  • The traffic to the application must be from clients able to load and execute New Relic's Browser JavaScript code and set cookies.
  • Clients accessing the application must be able to send data to New Relic through HTTP requests. HTTPS is required for Browser Pro features.

Most typical browser applications meet these requirements, but browser applications in restricted environments, such as hybrid mobile applications or those installed on unusual hardware such as point-of-sale terminals or consumer appliances, may have difficulty reporting data to New Relic.

For more information, see Instrumentation for browser monitoring and verify end-user network access.

Browser types

Instrumentation is compatible with every browser type, including Google Chrome, Mozilla Firefox, Microsoft Internet Explorer and Edge, and Apple Safari. The user interface is compatible with New Relic's supported browser versions.

Exceptions:

New Relic APM agents

You can deploy the New Relic Browser agent for apps monitored by New Relic APM, or you can deploy the Browser agent for your standalone apps. For more information, see the installation procedures.

If you are deploying New Relic Browser for an app using New Relic APM, make sure your New Relic agent supports Browser monitoring:

  • Java: Version 3.4.0 or higher
  • .NET: Version 2.20.25.0 or higher
  • Node.js: Version 1.4.0 or higher
  • PHP: Version 4.4.5.35 or higher
  • Python: Version 2.10.1.9 or higher
  • Ruby: Version 3.7.0.177 or higher

If you are using an established release of the Java or .NET agent as provided in your account settings, established releases earlier than the versions above support page load timing, but do not support Browser Pro features.

Supported frameworks

The New Relic Browser agent collects data on all front-end frameworks. However, the monitoring occurs on lower-level "primitives" that JavaScript frameworks use, so the level of detail collected by the instrumentation may vary depending on your specific framework.

If your application uses AngularJS and you want to use Browser's SPA monitoring capabilities, Zone.js versions 0.6.18-0.6.24 are not compatible with that feature.

Content Security Policy (CSP) considerations

In order to obtain accurate browser performance metrics, New Relic Browser requires the use of a small, inline JavaScript snippet. The Content Security Policy (CSP) 1.0 specification, which currently has the widest browser support, does not provide any way to selectively allow inline scripts to execute, so it is incompatible with New Relic Browser. In order to take advantage of New Relic Browser's powerful features, you cannot enable CSP 1.0 for your website.

When future CSP versions provide methods for webpages to selectively whitelist trusted inline scripts, and when a wide range of browser types support it, the New Relic Browser agent will be able to interoperate well with CSP. In the meantime, New Relic will continue to carefully review the inline JavaScript to prevent Cross-Site Scripting (XSS) and other potential vulnerabilities.

For more help

Additional documentation resources include:

Discuss Browser monitoring in the New Relic Online Technical Community! Troubleshoot and ask questions, or discuss JavaScript error reporting or AJAX timing in detail.

If you need additional help, get support at support.newrelic.com.