Web applications built using Single Page Application (SPA) principles minimize network traffic by transferring computing work for creating what the user sees to the browser. The initial page request downloads necessary data for constructing the application, with some possible exceptions. For example, HTML partials and fragments may be fetched dynamically from the backend 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 AngularJS Support.
Access Virtual Page Naming Rules
Open the browser application in which you are interested.
On the left navigation bar, click Configuration.
Click Instrumentation >.
- Select the Virtual Pages tab.
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 specify which virtual page is being accessed correctly.