Web applications built using Single Page Application (SPA) principles minimize network traffic by transferring to the browser itself much of the computing work for creating what the user sees. The initial page request downloads everything that is necessary for constructing all aspects of the application, with the possible exception of some data, including html partials and fragments, that may be fetched dynamically from the back-end in response to user interaction. The individual views that the user sees are known as virtual pages. Browser RUM supports virtual pages created using the AngularJS framework, sometimes known simply as Angular. In AngularJS, a virtual page is an individual View, comprised of the rendered template of the current route in the context of the main layout file. You can configure how AngularJS virtual pages are referred to and sorted in UI lists and dashboards. For more information on using Browser RUM with virtual pages, see Single Page Applications in Browser RUM - AngularJS.
Access Virtual Page Naming Rules
Access the Browser RUM configuration screen if you are not already there. On the left navigation bar, click Configuration.
- Select Instrumentation > End User Monitoring.
- Select the Web Page Naming, Error Detection, Thresholds, Percentiles, etc tab.
- Expand Configure how Virtual Pages will be named.
Whenever you make any changes, click Save to save the configuration.
Virtual Page Naming Rules
The logic for naming virtual pages is identical to that for naming regular pages, with one exception. Because AngularJS pages can use anchors (the part of the URL after the #) to distinguish among virtual pages, in these cases using the "What part of anchor should be used in page name" section allows you to correctly specify which virtual page is being accessed.