Access to this feature depends on your subscription level. SPA monitoring is only available with New Relic Browser Pro.
In order to set up Single Page Application (SPA) monitoring for New Relic Browser, make sure your app meets these New Relic SPA monitoring requirements.
Browser agent version
SPA monitoring requires an SPA-specific version of the Browser snippet, available for Browser agent version 885 or higher.
- To activate this snippet version for your application, enable your application for SPA monitoring.
- To check your version and integrate the updated snippet, follow the appropriate upgrade instructions.
SPA monitoring requires the
addEventListener Browser API and the Navigation Timing API. Both APIs are available in all modern browsers, including Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Internet Explorer (IE) versions 9 or higher.
Because SPA instrumentation works by wrapping low-level browser APIs, it is framework-agnostic. New Relic SPA instrumentation is compatible with most SPA frameworks, such as Angular, Backbone, Ember, and React. It can also instrument requests made using JSONP.
Below are known compatibility issues:
- If your application uses AngularJS and you want to use Browser's SPA monitoring capabilities, Zone.js versions 0.6.18-0.6.24 are not compatible with the SPA agent.
- The html2pdf.js library is not compatible with the SPA agent.
Security when collecting hash fragments
New Relic collects and saves hash fragments from route change URLs. If you use hashes to pass private or sensitive data, that data may be visible to your New Relic account users. Follow New Relic Browser's guidelines for security with data collection and reporting.
For more help
Additional documentation resources include: