On this page:
On this page:
Browser RUM supports virtual pages created using the AngularJS framework, sometimes known simply as Angular. The individual Views (a meaningful non-transient UI presentation) that the user sees are referred to as virtual pages. In AngularJS, a virtual page is comprised of the rendered template of the current route in the context of the main layout file.
Monitoring Support for AngularJS
AngularJS applications that have multiple Views use a route to move from one virtual page to another. You can use Browser RUM to instrument any virtual page that uses either of two routing engines,
Because virtual pages are constructed in the browser, normal page view metrics must be adjusted. In essence, what a metric for AngularJS must do is correlate the time between various routing events, using their timestamps. Metrics are calculated as follows:
|Full Metric Name||Short Metric Name||How Calculated|
|End User Response Time|
(not used for waterfall UI)
|HTML Download Time||DDT|
|HTML Download and DOM Building Time||DRT|
|DOM Building Time||DPT|
|DOM Ready Time|
(used instead of PLT for waterfall UI)
Because the two routing engines function in slightly different ways, what the AppDynamics event consists of differs slightly, based on the engine.
|AppDynamic Event Name||ngRoute Equivalent||ui-router Equivalent|
|load time of the last HTML fragment|
|response time of the last XHR requests|
|load time of the last resources|
|the latest one among |
Page Load Process Visualized
Visualized the page load process looks something like this:
Compare these to the standard page metrics, which are shown in Browser RUM Metrics.
Exclude Heartbeats or Background Requests from Timings
adrum.js, to the page:
View Correlated Server Times
Since there isn't a regular HTML page timing to which correlated server timings can be linked, to view server times you must drill down from the Dashboard or Snapshot virtual page view to the component XHR requests. The server times can be seen there.