Browser monitoring provides insights into how your application or site behaves when it is loaded in a web browser. Browser only records performance data, as explained in this document. It does not record any data used or stored by the monitored application unless you explicitly configure it to do so.
For most data types, browser transmits the data securely using HTTPS encryption. The browser agent transmits data to New Relic's collectors by using either of the domains
Here is a summary of the types of data reported by browser monitoring.
The browser agent uses the HTTP
referer attribute to track page URLs. URLs can sometimes contain potentially sensitive user-entered query data (for example, a user's name). For data security reasons, browser does not record or collect URL query strings.
Browser uses the visitor's IP address to enrich data for additional visitor segmentation. Details such as the
geoID are mapped to browser data from the IP address. For data security reasons, browser does not retain the visitor's IP address for reporting. The IP address is obtained in the HTTP header from the request to the New Relic collector.
New Relic does not retain the visitor's IP address after the attributes have been mapped. The IP address value is overwritten within 24 hours of data being collected.
Browser determines the browser type from the
User-Agent header and the geographical location based on the browser's IP address. New Relic does not retain the IP address, only the country and region associated with the performance data.
nr.js) is hosted. The domain name for the file (
js-agent.newrelic.com) remains static, but the number in the path (version) may change periodically.
If your end users are behind a firewall or proxy and do not have access to the CDN or to New Relic's networks (including
bam-cell.nr-data.net), browser monitoring will not work.
Browser monitoring creates cookies in the end user's browser. If the user has cookies disabled, page load timing (sometimes referred to as real user monitoring or RUM) will not be able to track sessions properly. Also, if the user has an older browser that does not support the Navigation Timing Specification API, page load timing will not be able to track response times as accurately.
New Relic's cookies generated by browser agents older than version 995 may not contain the
secure attribute. This is because page load timing data transmission in versions before version 995 use HTTP when the page is HTTP, but use HTTPS when the page is HTTPS. All browser agent versions above version 995 will always use the
secure flag for cookies and transmit over HTTPS.
For customers subject to special guidelines for cookie collection, such as those under the EU GDPR/PECR ICO Guidelines, we now provide the option to disable cookie collection for your application. Please see our browser agent v1169 release notes for more information.
If your site uses P3P, it must be configured to allow these cookies.
Page load timing metrics are reported to New Relic using a Script
GET, also known as a JSONP request. The Script
GET returns a value that is subsequently stored in a cookie and used to trigger trace capturing.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.