AppDynamics Application Intelligence Platform

3.9.x Documentation

PDFs

Learn by Watching

Doc Maps

Skip to end of metadata
Go to start of metadata

Key Web EUEM metrics are displayed on the Geo, Page, Iframe, and Ajax dashboards.  They can also be seen on the All Pages and Top Pages lists and in the Metric Browser. In addition, the Metric Browser gives you the ability to view these metrics in the context of Ajax requests, iframes, applications, base pages, browsers, devices, and geographic locations.

You can build custom health rules based on Web EUEM Page, Ajax, and iframe metrics in the health rule builder. Use these rules to automatically monitor key metrics in your installation. For more information, see Health Rules.

Web EUEM Timing Metrics Overview

The following provides an overview of the basic Web EUEM page and iframe timing metrics.  For key Ajax metrics, see here.  Metrics in black are available from both modern browsers that support the Navigation Timing API, and older browsers.  Metrics in blue are available only from NavTime browsers.  You may see a value of unknown for some metrics taken using older browsers.

When users begin to load the first instrumented page, a timer is started by the JavaScript agent.  The timer, or the NavTime responseStart, begins the first page timing.

For all subsequent pages, a cookie is set by the agent when the Prompt for unload event happens on the current page.  This cookie, or the NavTime navigationStart, initializes a fuller picture of the entire page loading sequence.  

(info) Because a NavTime browser always sets navigationStart, you can get this information from it even on the first page a user loads from your site.

Navigation Timing capable browsers also provide highly granular information on connection details.

Web EUEM Metrics Defined

Time metrics are the average times, in milliseconds, over the time range selected in the Controller UI or REST API call. The three letter abbreviation is the short name as it is recorded in the web beacon.  

NameShort NameNavTiming Capable
Browsers
+
Browsers without NavTiming SupportAvailable
For . . .
Definition
Ajax Callback Execution Time
In 3.7 this metric was called Document Processing Time 
DPT

responseEnd to
domContentLoadedEventStart in the context of the Ajax object

responseEnd to
 domContentLoadedEventStart in the context of the Ajax object
Ajax RequestsTime for the browser to process the Ajax response; this typically includes the time to apply the response data to the DOM
Ajax Response Download Time
In 3.7 this metric was called Document Download Time
DDTresponseStart to 
responseEnd in the context of the Ajax object
responseStart to 
responseEnd in the context of the Ajax object
Ajax RequestsTime for the browser to download the complete Ajax response
Ajax Request Errors per MinuteBased on ARE entries  Ajax Requests, App, Browser, Device and GeoTotal number of Ajax requests that generate an error per minute
Ajax Requests per MinuteBased on PLC entries  App, Browser, Device, and Geo

Total number of Ajax requests per minute

Application Server Calls per Minute   Ajax Requests App, Base Pages, Browser, Device, Geo, and iframesNumber of requests that actually hit the application server, rather than a cache
Application Server Time   Ajax Requests,  App, Base Pages, Browser, Device, Geo, and iframe Processing time for requests on the application server
DOM Building Time
In 3.7 this metric was called Document Processing Time
DPTresponseEnd to
domContentLoadedEventStart
N/AApp, Base Pages, Browser, Device, Geo, and iframesTime for the browser to build the Document Object Model (DOM) and make it available for JavaScript to apply rendering logic
DOM Ready TimeDOMnavigationStart to domContentLoadedEventStartTime between the writing of the starttime cookie on the previous page and an internal handler's onready event, similar to jquery.onready()App, Base Pages, and Geo Interval between the time that a user initiates a request and the time that the DOMContentLoaded event (or the internal handler's onready event) occurs
Domain Lookup TimeDNSdomainLookupStart to 
domainLookupEnd
N/AApp, Base Pages, Browser, Device, Geo, and iframesTime to complete the domain lookup  portion of the server connection time
End User Response TimePLTnavigationStart to 
loadEventEnd
Time between the writing of the starttime cookie on the previous page and the onload eventAjax Requests,  App, Base Pages, Browser, Device, Geo, and iframesAverage interval between the time that a user initiates a request and the completion of the page load of the response in the user's browser. In the context of an Ajax request, it ends when the response has been completely processed.
First Byte TimeFBTnavigationStart to responseStartTime between the writing of the starttime cookie on the previous page and when the page's JavaScript agent begins executingAjax Requests, App, Base Pages, Browser, Device, Geo, and iframesInterval between the time that a user initiates a request and the time that the browser receives the first response byte. In the context of an Ajax request, First Byte Time is the interval between the Ajax request dispatch and the time that the browser receives the first response byte. 
Front End TimeFETresponseStart to 
loadEventEnd
Time between when the page's JavaScript agent begins executing and  the onload event.App, Base Pages, Browser, Device, Geo, and iframesInterval between the arrival of the first byte of text response and the completion of the response page rendering by the browser. Includes HTML Download, DOM Building Time, and Resource Fetch Time.
HTML Download and DOM Building Time
In 3.7 this metric was called Document Ready Time
DRTresponseStart to 
domContentLoadedEventStart
Time between when the page's JavaScript agent begins executing and an internal handler's onready event, similar to jquery.onready().App, Base Pages, Browser, Device, Geo, and iframesTime to make the complete HTML document (DOM) available for JavaScript to apply rendering logic. Includes the HTML Download and the DOM Building Time.
HTML Download Time
In 3.7 this metric was called Document Download Time
DDTresponseStart to 
responseEnd
N/AApp, Base Pages, Browser, Device, Geo, and iframeTime for the browser to download the complete HTML document content
Iframe Requests per MinuteBased on PLC entries  App, Browser, Device,  and GeoTotal number of iframe requests per minute
Page Requests per MinuteBased on PLC entries  App, Browser, Device, and GeoTotal number of Page requests per minute. This is the metric displayed across most of the UI.
Page views with JavaScript Errors per minuteBased on EPM entries  App, Base Pages, Browser, Device, Geo, and iframesTotal number of page views that contain JavaScript errors per minute
Resource Fetch Time
In 3.7 this metric was called Page Render Time.  
PRTdomContentLoadedEventStart to 
loadEventEnd
Time between an internal handler's onready event, similar to jquery.onready(), and onload.App, Base Pages, Browser, Device, Geo, and iframesTime for the browser to complete the download of remaining resources, including images, and finish rendering the page
Response Available TimeRATrequestStart to 
responseStart
N/AApp, Base Pages, Browser, Device, Geo, and iframesInterval between the beginning of the processing of the request on the browser to the time that the browser receives the response. Includes time in the network from the user's browser to the server.
Requests per MinuteBased on PLC entries  Ajax Requests,  App, Base Pages, Browser,  Device, Geo, and iframessTotal number of requests (Page + Ajax + iframe) per minute
Server Connection TimeSCTnavigationStart to 
requestStart
N/AApp, Base Pages, Browser, Device, Geo, and iframesInterval between the time that a user initiates a request and the start of fetching the response document from the server or application task. Includes the time spent on redirects, domain lookups, TCP connects and SSL handshakes. 
SSL Handshake TimeSSLsecureConnectionStart to 
connectEnd
N/AApp, Base Pages, Browser, Device, Geo, and iframesTime taken to complete the SSL handshake
Synthetic Requests per Minute   Ajax Requests, App, Base Pages, Geo, and iframesTotal number of requests from synthetic monitoring agents, like Web Page Test, per minute
TCP Connect TimeTCPconnectStart to 
connectEnd.
N/AApp, Base Pages, Browser, Device, Geo, and iframesTime to complete the TCP connect portion of the server connection time, the equivalent of one network round trip of latency

+ NavTiming capable browsers support the W3C Navigation Timing API.

 

If you are upgrading from controller version 3.7.x to 3.8+, the data that was stored previously in the database under old names (Document Download Time, Document Ready Time, Document Processing Time, and Page Render Time) is no longer surfaced to the user interface. The data is still in the database, however, under the old name, and is visible in the metric browser.

Ajax Metrics Availability

Because Ajax requests occur in the context of the larger page, these four core metrics are always available, regardless of the browser type.

For more information on which browsers support the Navigation Timing API, see the Can I Use web site.

Resource Timing Metrics

For browsers that support the Resource Timing API, the following additional metrics are available based on resources that are loaded during Resource Fetch Time:

Name
Definition
Scripts Loaded per PageviewNumber of JavaScript files (*.js) downloaded with this pageview
Images Loaded per PageviewNumber of image files (*.bmp, *.gif, *.jpeg, *.jpg, *.png, *.webp) files downloaded with this pageview
Resources Loaded per PageviewNumber of all resource files (the above plus *.css, *.svg, *.htm, *.html, *.ttf, *.woff, *.otf, *.eot) files downloaded with this pageview

Learn More