- Webserver and systems: Browser App Monitoring occurs on the user's browser, not on the server. Processing time does not have an impact on your CPU consumption.
In addition, we take additional steps to minimize any potential impact on the apps and webpages being monitored. For example, the "loader" script is loaded synchronously in the
<HEAD> in order to ensure monitoring is enabled for the entire life cycle of the page. This script is included inline, which eliminates the need for another roundtrip network request to a content delivery network (CDN). The "loader" comes with the initial page load.
Later in the life cycle of the page, New Relic loads an additional monitoring script asynchronously. This script should not have any perceivable effect to the user and is included in the overall overhead of less than 15ms per page.
Browser monitoring also minimizes network traffic for the end user by aggregating data locally (in the client) and sending it back to New Relic on
load, at periodic intervals, on
unload, or when data has been collected. (During the browser session's idle periods, transmissions may not be required.)
For more help
Additional documentation resources include: