Compatibility and requirements for New Relic Browser

New Relic Browser includes strict security measures to provide a robust, standalone product with browser monitoring features. Before you install the New Relic Browser agent, make sure your system meets these requirements.

Basic requirements

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

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

Browsers that subscribe to a disconnect list or that use content filtering extensions such as AdBlock may not be able to send data to New Relic. For example, if you are using the Enhanced Tracking Prevention disconnect list for Mozilla Firefox 69.0 or higher, you will need to change the default configuration.

Most typical browser applications meet these requirements. However, browser applications in restricted environments may have difficulty reporting data to New Relic; for example:

  • Hybrid mobile applications
  • Applications installed on unusual hardware, such as point-of-sale terminals or consumer appliances

For more information, review the instrumentation for browser monitoring documentation, 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 Comments
Paint timings

The firstPaint and firstContentfulPaint attributes in BrowserInteractions and PageView events are only compatible with:

  • Chrome 60+ for desktop and mobile (Android webview & Chrome for Android)
  • Opera 47+ for desktop
  • Opera 44+ for Android mobile
  • Samsung Internet for mobile

AJAX timing features are not available with:

  • Chrome for iPhone and iPad
  • IE 7 and 8
PageAction events

PageAction events in New Relic Insights require a browser that fully supports cross-domain XMLHttpRequests. Internet Explorer versions 9 and lower cannot record PageAction events.

Session traces

Session traces are reported only from browsers that support the Resource Timing Specification.


New Relic can only monitor browsers that are compatible with SHA-256.

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:

  • C SDK: Version 1.0.0 or higher
  • Go: Version 2.5.0 or higher
  • Java: Version 3.4.0 or higher
  • .NET: Version or higher
  • Node.js: Version 1.4.0 or higher
  • PHP: Version or higher
  • Python: Version or higher
  • Ruby: Version or higher

Some New Relic accounts use an APM agent established release. If the established release is earlier than the agent version that supports Browser monitoring, the established release will support page load timing, but it will 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.

Exceptions Comments
Zone.js If you're using AngularJS and you want to use Browser's SPA monitoring capabilities, note that Zone.js versions 0.6.18-0.6.24 are not compatible with Browser. The Browser agent will cause an error when tests are run in Cypress. This will only affect customers running tests with the Browser agent present in their code. Production applications should not be affected.
html2pdf.js Not compatible with our SPA-enabled Browser agent due to the way this library wraps promises. If you're using this library, we recommend the Browser Pro agent.

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. New Relic carefully reviews the inline JavaScript to prevent Cross-Site Scripting (XSS) and other potential vulnerabilities.

Content Security Policy Level 2 adds restrictions to the types of JavaScript allowed, such as inline scripts. It also limits which domains can load scripts during page load.

If your website does not allow any third-party hosted JavaScript to run, you must request a CSP exception in order to install the New Relic Browser agent.

To request a CSP exception:

  1. Follow your organization's standard procedures to contact your web or security team.
  2. Add both of these New Relic Browser domains to your CSP whitelist:
    • This is where the New Relic Browser agent is hosted. The Browser agent download requires three files to run. Two are downloaded after the initial agent is run to continue capturing performance data.
    • This is the endpoint where the New Relic Browser agent receives data from your site.

Here is example HTML to add to the head of your site:

Content-Security-Policy: default-src 'self'

CSP has multiple levels of complexity. Depending on how it is applied to your pages, it will impact how the Browser agent runs.

For more help

Recommendations for learning more: