Analysis snapshot

The Analysis snapshot provides a starting point of the troubleshooting process. The inspection points focus on commonly encountered web application problems. For each of the inspection points, there is an overview of what analysis was done, why this analysis matters, and the result of the test.

Click View additional data and recommendations to display these sections:

  • Areas to Investigate which provides specific recommendations, when identified, on areas that you should investigate. This overview is designed to help you identify potential problem areas, and to assist you in localizing issues, either by geography or network topography, or both
  • Performance Metrics for this test by Host and by Site
  • Overall System Health

Inspection points

The Analysis snapshot provide information about these inspection points.

Average DNS time threshold

If the arithmetic average DNS Lookup time for all lookups for all hosts in the test time frame exceeds 90 ms, this test fails.

Average DNS time threshold failure message

Current Average DNS Lookup time exceeds 90 ms.

DNS time banding

Each Host's DNS lookup time is collected into a histogram by second; for example, the number of DNS lookups between 0 and .999 seconds, between 1 and 1.999 seconds, and so on.

If the number of DNS lookups between 2 and 2.999 seconds is more than 25% of the total number of DNS lookups for that hostname, this test fails.

DNS time banding failure message

DNS Time results for the following hostnames are over 25% within the 2 second band; this suggests heavy load on the DNS servers:

  • <hostname1>
  • <hostname2>

Average initial connection time threshold

If the arithmetic average initial connection time for the measurements in the test timeframe is greater than .5 seconds, this test fails.

Average initial connection time threshold failure message

Current average Initial Connection time exceeds threshold of 500 ms.

Connection time banding

Connection Time results for the following host IPs are 80% within the 3/9/21 second bands; this suggests heavy load on the web servers and/or load balancers.

  • <hostIP>
  • <hostIP>
Connection time banding failure message

Connection Time results for the following host IPs are 80% within the 3/9/21 second bands; this suggests heavy load on the web servers and/or load balancers.

  • <hostIP>
  • <hostIP>

HTTP persistent connections enabled

For each measurement in the test time frame, if a given host has the same number of connections as objects, and the number of objects is greater than 2, the host is presumed to have persistent connections disabled, and this test fails.

Failing hosts are displayed in hostname order.

HTTP persistent connections enabled failure message

HTTP Persistent Connections appear to be disabled for the following hosts:

  • <hostIP> at <hostname> had X connections for X objects. This increases network overhead, causing delays in page loads, and greater stress on the servers.

Average SSL time threshold

If the arithmetic average SSL time for the measurements in the test timeframe is greater than .5 seconds, this test fails.

This test is removed if the test did not have any SSL time.

Average SSL time threshold failure message

Current average SSL Handshake time exceeds 500 ms.

Page element consistency check

For each measurement in the test time frame, each unique object URI is checked to see if the object failed more than 25% of the time, where object failure is currently defined as having a response code above 399. If any object has a failure rate above 25%, this test fails.

Page element consistency check failure message

The following objects consistently fail (above 25% failure):

  • <object URI>
  • <object URI>

Dynamic objects analysis

All hosts will be displayed by hostname, and only objects failing the threshold and above .500 seconds will be displayed, in descending order.

Threshold is determined in the following manner: All "static" objects, where the URL path ends with .gif, .jpg, or .png, will get their first byte response time analyzed for geometric average and deviance by hostname, and the threshold will be the average + 3 deviances. If no static objects exist for a given hostname, its initial connection times will be used instead.

Dynamic objects analysis failure message

Probable Dynamic objects and Threshold First-Byte Response Times by Host:

  • hostname-0.071s
  • objurl-3.235s
  • objurl-3.004s