Beginning in February 2020, AppDynamics switched from Semantic Versioning to Calendar Versioning for some agents and the first deployments of SaaS Controllers. In March 2020, the entire product suite will use Calendar Versioning.
Related pages:
Your Rating:
Results:
28
Key Browser RUM metrics are displayed on the Geo, Pages & AJAX Requests, and Usage Stats dashboards. They can also be seen on the All Pages and Top Pages lists and in the Metric Browser.
In addition, the Metric Browser enables you 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 Browser RUM 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.
Browser RUM Timing Metrics Overview
The following provides an overview of the first Browser RUM page and iframe timing metrics. For key Ajax metrics, see Ajax Metrics Availability. 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, the JavaScript Agent starts a timer. The timer or the NavTime responseStart starts the first-page timing.
Because a NavTime browser always sets navigationStart, you can retrieve this information even on the first page a user loads from your site.
NavTiming-capable browsers also provide highly granular information on connection details.
Browser RUM Metrics Defined
Timing 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.
| Name (Short Name) | NavTiming Capable Browsers1 | Browsers without NavTiming Support | Available For . . . | Definition |
|---|---|---|---|---|
| Ajax Callback Execution Time (DPT) |
| responseEnd to domContentLoadedEventStart (context of the Ajax object) | Ajax Requests (XHR, Fetch API) | Time for the browser to process the Ajax response. |
| Ajax Response Download Time (DDT) | responseStart to responseEnd(context of the Ajax object) |
| Ajax Requests (XHR, Fetch API) | Time for the browser to download the complete Ajax response. |
Ajax Request Errors per Minute (Short name based on |
| Total number of Ajax requests that generate an error per minute. | ||
Ajax Requests per Minute (Short name based on |
| Total number of Ajax requests per minute. | ||
| Application Server Calls per Minute |
| Number of requests that actually hit the application server, rather than a cache. | ||
| Application Server Time (also called Server Time in the UI) |
| Processing time for requests on the application server. | ||
| Browser Queue Time |
| |||
| DOM Building Time (DPT) | responseEnd to domContentLoadedEventStart | N/A |
| Time for the browser to build the Document Object Model (DOM) and make it available for JavaScript to apply rendering logic. |
| DOM Ready Time (DOM)2 | navigationStart to domContentLoadedEventStart | Time between the writing of the |
| 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 Time (DNS) | domainLookupStart to domainLookupEnd | N/A |
| Time to complete the domain lookup portion of the server connection time. |
End User Response Time (PLT)2 | navigationStartto loadEventEnd | Time between the writing of the |
| Average 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. For information about End User Response Time for SPA2 pages, see SPA2 Metrics. |
First Byte Time (FBT)2 | navigationStart to responseStart | Time between the writing of the |
| Interval 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 Time (FET) | responseStart to loadEventEnd | Time between when the page's JavaScript Agent begins executing and the onload event. |
| Interval 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 (DRT) | responseStart to domContentLoadedEventStart | Time between when the page's |
| Time 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 (DDT) | responseStart to responseEnd | N/A |
| Time for the browser to download the complete HTML document content. |
Iframe Requests per Minute (Short name based on |
| Total number of iframe requests per minute. | ||
| Images Loaded per Pageview |
| Total number of images in a Calculated after page has completely loaded. | ||
Page Complete Time (PCT) | N/A | N/A |
| Total time for the browser to render all visual page elements (both in and out of the viewport). Available for SPA base pages only. For information about Page Complete Time for SPA2 pages, see SPA2 Metrics. |
Page Requests per Minute (Short name based on |
| Total number of Page requests per minute. This is the metric displayed across most of the UI. | ||
Page views with JavaScript Errors per minute (Short name based on |
| Total number of page views that contain JavaScript errors per minute. | ||
| Resource Fetch Time | domContentLoadedEventStartto loadEventEnd | Time between an internal handler's onready event, similar to jquery.onready(), and onload. |
| Time for the browser to complete the download of remaining resources, including images, and finish rendering the page. |
| Resources Loaded per Pageview |
| Total number of resources in a Calculated after the page has completely loaded. | ||
Requests per Minute (Short name based on |
| Total number of requests (Page + Ajax + iframe) per minute. | ||
| Scripts Loaded per Pageview |
| Total number of scripts in a Calculated after the page has completely loaded. | ||
| Server Connection Time (SCT) | navigationStart to requestStart | N/A |
| Interval 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 Time (SSL)3 | secureConnectionStart to connectEnd | N/A |
| Time taken to complete the SSL handshake. |
| TCP Connect Time (TCP) | connectStart to connectEnd | N/A |
| Time to complete the TCP connect portion of the server connection time, the equivalent of one network roundtrip of latency. |
| Total Resource Redirect Time |
| Time for all redirects associated with fetching resources. Calculated after the page has completely loaded. | ||
Visually Complete Time (VCT) | N/A | N/A |
| Total time for all visual elements within the first screen (above-the-fold content) to load in an end user’s browser. For information about Visually Complete Time for SPA2 pages, see SPA2 Metrics. |
Overview
Content Tools