detect virtual pages
measure the end-to-end time for virtual pages
name virtual pages
Controller / EUM Server 4.4.3+ (for on-premises deployments)
- IE 10 and Edge is supported. IE 10+ and Edge cannot be in compatibility mode with IE 9 or older browsers.
Enable/Disable SPA2 Monitoring
false, so to enable SPA2 monitoring, you must set
Disable SPA2 Monitoring
To disable SPA2 auto-instrumentation, just set
false. Although the default value for
false, you are recommended to set the configuration to false and not just remove it.
Migrate from SPA1 to SPA2 Monitoring
To migration from SPA1 to SPA2 monitoring:
- Read SPA1 and SPA2 Monitoring to confirm that your use case is suitable for SPA2.
- Meet the SPA2 requirements.
- Enable SPA2 monitoring.
SPA2 Monitoring Compatibility
Metrics such as DOM ready, # of digests, etc., are no longer measured and reported for virtual pages.
Fetch API Support for SPA2 Monitoring
For Angular.js and Angular 2-9 applications, follow these steps to ensure Fetch API calls are monitored.
How SPA2 Monitoring Works
From the base page, the user clicks a button to view products. The URL changes as the virtual page is loaded through a combination of previously downloaded content and from new content fetched through Ajax requests.
|User actions and the browser activity cease for five seconds. The browser activity includes requesting resources, making Ajax calls, and so on.|
Browser RUM calculates metrics differently for base pages, Ajax requests, and virtual pages. The diagrams below demonstrate the differences between base page and virtual page metrics from the end-user perspective. See Browser RUM Metrics for metric definitions.
For base pages, Browser RUM calculates End User Response Time (EURT), Visually Complete Time (VCT), and Page Complete Time (PCT). For virtual pages, Browser RUM calculates EURT and VCT.
End User Response Time
End User Response Time (EURT) calculates the total time for all content (visual and non-visual) to be loaded on a page.
Visually Complete Time
Visually Complete Time (VCT) calculates the point in time when the browser has finished loading all visual content in the viewport.
Page Complete Time
Page Complete Time (PCT) is a SPA2 metric for base pages only. PCT calculates the point in time when the browser has finished loading all visual content on the page, regardless of whether the content is in or outside the viewport.
Configure Virtual Page Monitoring
maxInactiveTime tracks when activities like networking and DOM changes stop. Though
maxInactiveTime is not directly included in metrics like EURT, for example,
maxInactiveTime confirms the EURT stop time. For larger pages, you may want to increase the
maxInactiveTime to accurately track when all page activity is complete. The default
maxInactiveTime is set to 8 seconds.
In this example, the
maxInactiveTime is increased to 10 seconds.