Page tree

The following tables describe the BMC Real End User Experience Monitoring web application attributes and metrics created from the web traffic data collected, identified, and used in analysis. You can directly query the metrics or drill down to the metrics through dashlets, Watchpoints, reports, and session analysis.

Latency (response time) metrics

Metric1

Description

E2E Latency

Time it takes to deliver an object or page to the end user, starting from the time the first packet in the request is received until the browser acknowledges the delivery of the final packet in the response

This metric measures the end-to-end latency of the entire object or page, including HTTP redirects. The system calculates this metric as the difference between the start time of the earliest element and the end time of the last element.

Host Latency

Time for the server to process the user's request and to generate a response

This metric focuses on application responsiveness, ignoring the overhead of the network and the payload transfer time. Host latency time is calculated by totaling all latencies from the objects as effort. The system uses these effort totals to determine the percentage of effort required by the host. That percentage is then applied to the end-to-end time (minus any idle time for the page) to map the host effort to real time. Host Latency is typically used by SaaS vendors or other service providers that do not want poor network quality to affect the performance numbers.

Network Latency
Time for the object or page data to be transferred across intervening networks
SSL Latency
Time for the web system to negotiate SSL encryption for this object or page (not applicable if the page was not encrypted)
Redirect Latency
Time spent redirecting the user to this page
Page Render Time

Time required for the browser to load the page

The page-render time (PRT) metric measures the time to render all content on a page, when all or some of the content comes from a source other than your origin server. The system uses a special web beacon target injected into web pages to derive PRT. To monitor the performance of content served by Akamai, you would use the page-render time metric. PRT is often used for applications with any of the following characteristics:

  • The application embeds third-party content in the pages.
  • The application performs most processing on the client during content loading.
  • The application uses content delivery networks (CDNs) to cache content closer to the user. 

Because the PRT metric measures from the start of page loading in the browser until the onLoad event, it incorporates many client-side impacts that would not be apparent to the server.

Note: To use the PRT metric, you must first configure the reporting of page-render time.


Cache Fetch

Time required, after redirects, to search or fetch page content from the browser's cache

This metric is useful for optimizing the page. For example, this metric can show whether time was spent fetching cache data on a page that contains objects with error 304. 

Browser instrumentation is required to capture this metric.

DNS Resolve

Time required to perform DNS lookup for the domain, measured from the beginning of a page load

This metric measures time for container objects only. DNS lookups for other objects in pages that are from different hosts are not included.

Browser instrumentation is required to capture this metric.

TCP Connect

Time measured from the start of a TCP session (handshake) to the point at which the browser is ready to send an HTTP request (SSL negotiation)

This metric can include the SSL time through the browser metrics for the container.

DOM Interactive

Time measurement from the point at which the navigation starts until the point at which the browser considers the page to be interactive

At the point of Document Object Model (DOM) Interactive, the browser has finished parsing the requested resource, but the subcomponents are not yet loaded. Although the page components are not fully loaded, the page appears usable to the end user.

Browser instrumentation is required to capture this metric.

DOM Loading to Interactive

Time measurement from the point at which the browser begins parsing the requested resource to the point identified in the DOM Interactive metric

This metric indicates how much time the browser spent processing the page content.

DOM Content Loaded

Time required to process content from start to finish

Browser instrumentation is required to capture this metric.

DOM Completed

Time measurement from the point at which the user starts navigation to the point at which the DOM was loaded and most processing is finished

Some changes could still occur as part of on.load events, which are not included in the time measured.

Browser instrumentation is required to capture this metric.

Loaded

Time from the beginning of the navigation to the point at which the page is considered finished by the browser

Although you should not compare their times, this metric is similar to the End-to-End Latency metric, which passively collects network-based metrics.

Browser instrumentation is required to capture this metric.

Idle time

Total time of inactivity after a page was loaded in the browser

Idle time is the sum of all gaps between the end of one object and the start of the next object on a page. This metric indicates inefficiencies in page loading.

Think time

Total time of inactivity in a session.

Think time measures the gap between the end of one page and the start of another page in a session.

1.All latency metric times are measured in milliseconds.

Application metrics and attributes

Metric or attribute

Description

Page Name

Unique page names that meet the query criteria and are shown as a percentage of the total page count

Application Name

Unique object names that meet the query criteria and are shown as a percentage of the total page count

Size (B)

Size of this object or page (request and response), in bytes

Object Count

Number of content hits on a certain page. This parameter applies for page queries only and is not displayed for object queries.

Error Condition

Error-detection rule (error severity), created on the data provider, that detects an error when a given event occurs in the web traffic

Info Condition

Error-detection rule (informational severity), created on the data provider, that detects an error when a given event occurs in the web traffic

User attributes

Attribute

Description

Browser

Name of the browser that the user is using, as it is set up in the data provider

City

City the user is using as derived from the IP geolocation

URI

Uniform resource identifier (URI) of the object that is requested. The URI is the full path and resource obtained from the URL, starting from the first slash (/) character.

Client IP

IP address of the client that generated the request

Infrastructure metrics and attributes

Metric or attribute

Description

Host

Value of the host as it is displayed in the HTTP header

Server ID

Name or identifier of the server or network infrastructure component that serviced the request

Server IP

IP address of the server that responded to the request

TCP OOO

Number of out-of-order TCP segments in the transmission

This metric is usually an indication of route flapping or poor link load balancing.

TCP RTT (ms)

Average TCP round-trip time (RTT) of all objects or pages between the client and the server, in milliseconds

TCP RTX

Number of TCP segments retransmitted. A high number of retransmissions might indicate traffic shaping or packet loss.

Errored and aborted report metric

MetricDescription
Errored and Aborted

Hits Open link with error code 24 (server too busy to respond) and error code 25 (server aborted mid-response)

AbortedHits with error code 33 (client aborted request) and error code 34 (server aborted request)
ErroredAll other hits with errors (including error condition 21, 22, or 23 client or server timeout conditions)
Good

Hits without any errors or aborts