Browser monitoring includes strict security measures to provide a robust, standalone product with browser monitoring features. Before you install the browser agent, make sure your system meets these requirements.
Want to try out our browser monitoring agent? Create a New Relic account... It's for free, forever! No credit card required.
To report data to 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
For more information, review the instrumentation for browser monitoring documentation, and verify end-user network access.
The browser agent officially supports the following browser versions:
- Chrome (previous 10 versions)
- Safari (previous 10 versions)
- Firefox (previous 10 versions)
- Edge (previous 10 versions)
Instrumentation and specific features may be compatible with other browsers or versions.
The user interface is compatible with New Relic's supported browser versions.
AJAX timing features are not available with:
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.
When you use browser monitoring with cookies, New Relic's cookies are a third-party cookie on your site, and may not store or work on certain web browsers used by your visitors. See the applicable browser's websites for details about their compatibility with third-party cookies.
You can deploy the browser agent for apps monitored by APM, or you can deploy the browser agent for your standalone apps. For more information, see the installation procedures.
If you're deploying browser for an app using APM, make sure your agent supports browser monitoring:
- Go: Version 2.5.0 or higher
- Java: Version 3.4.0 or higher
- .NET: Version 18.104.22.168 or higher
- Node.js: Version 1.4.0 or higher
- PHP: Version 22.214.171.124 or higher
- Python: Version 126.96.36.199 or higher
- Ruby: Version 188.8.131.52 or higher
If you're using AngularJS and you want to use our SPA monitoring features, note that Zone.js versions 0.6.18 to 0.6.24 are not compatible with browser. In all cases, the browser agent must be loaded before Zone.js to avoid errors.
Browser is unable to properly instrument the
This will only affect customers running tests with the browser agent present in their code. Production applications should not be affected.
This library is not compatible with our Pro+SPA agent due to the way this library wraps promises. If you're using this library, we recommend selecting the Pro agent type.
Content Security Policy (CSP) considerations
When requesting a CSP exception, follow your organization's standard procedures to contact your web or security team.
default-src directive (instead of
In older browsers
image-src or requests for images can be a possible exception that should be accounted for.
Add to the
Add to the
The agent attempts to send payloads to subdomains of