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.
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 220.127.116.11 or higher
- Node.js: Version 1.4.0 or higher
- PHP: Version 18.104.22.168 or higher
- Python: Version 22.214.171.124 or higher
- Ruby: Version 126.96.36.199 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 are 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.|
Content Security Policy (CSP) considerations
To request a CSP exception:
- Follow your organization's standard procedures to contact your web or security team.
- Add both of these New Relic Browser domains to your CSP whitelist:
https://js-agent.newrelic.com: 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.
https://bam.nr-data.net: 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' https://js-agent.newrelic.com https://bam.nr-data.net
CSP has multiple levels of complexity. Depending on how it is applied to your pages, it will impact how the Browser agent runs.