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.
To report data to New Relic Browser, your application must at a minimum meet two basic requirements:
- 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
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.
AJAX timing features are not available with:
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 188.8.131.52 or higher
- Node.js: Version 1.4.0 or higher
- PHP: Version 184.108.40.206 or higher
- Python: Version 220.127.116.11 or higher
- Ruby: Version 18.104.22.168 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.
|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.|
|Cypress.io||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
When requesting a CSP exception, follow your organization's standard procedures to contact your web or security team.
script-srcdirective. This is required because the agent is installed by including an inline script.
script-srcdirective. This is where additional script files that the agent requires are hosted.
script-srcdirective. This is where the agent sends its collected data. One of the calls to this URL is a JSONP call, which means that the URL must be allowed as a script source.
connect-srcdirective affects the URLs that scripts can call (e.g. using the XMLHttpRequest interface). If you have CSP restrictions specifically around this directive, then add this URL as an exception.
Note: All of these exceptions can also be added to the fallback
default-src directive (instead of