Using the HTTP Server View
When you create any HTTP Server or Page Load test, you get access to the HTTP Server view. The HTTP Server view leverages the ThousandEyes standard layout, documented here.
This article highlights specifics shown in the HTTP Server view.
Example
This example shows the result of an HTTP Server test:
View Specifics
The HTTP server test measures the following metrics:
Availability: Percentage of time that the site is available, aggregated across all agents.
Response time: Also known as Time-to-first-byte, this is the time elapsed from the beginning of the request (before DNS request) until the client receives the first byte of the response from the server.
Throughput: is calculated by dividing the total wire size to the receive time and expressed in MB/s
For more details on available metrics, see this article.
The HTTP Server view shows two different data views, depending on whether or not a location is selected, and varies somewhat depending on which metric is selected. Details for each selected metric are shown below.
Availability
The availability for a given agent should be 100% if the HTTP status code is 2xx or 3xx, and 0% otherwise. The average availability can take any value from 0% to 100%.
Without a Location Selected
When no location is selected, the computed averages area shows a breakdown by error type. Definitions of the possible error types are as follows:
Error Type Error Definition DNS
Failure to resolve a domain name to one or more IP addresses using DNS
Connect
Failure to complete a TCP 3-way handshake (SYN, SYN-ACK, ACK)
SSL (if test target using SSL/TLS)
Failure to complete SSL/TLS negotiation
Send
Failure to complete sending of an HTTP GET or POST request
Receive
Failure to receive a valid and complete HTTP response
HTTP
Receiving an HTTP response code that is not (default) 2XX or 3XX, or not the desired HTTP status code of the response as configured in Advanced Settings of the test
Content (optional)
Failure to match returned content to an expression in the Verify Content field
Without a location selected, the timeline shows a chart showing the average availability calculated from all locations globally. The following image shows an example of a timeline for the availability metric:
The table view shows by-location metrics for each of locations used in the test. This includes location name, date and time that the data was captured, destination server IP, HTTP response code, number of redirects, and error type/details, if applicable.
With a Location Selected
The computed averages area shows the status (a green or red square) and HTTP response code, as well as a popup to view the response headers from the target website. When you click the response headers, a dialog shows the content of the response.
When you click View Headers, a popup with two tabs shows response and request headers:
With a location selected, the timeline shows a chart showing average availability for that location, charted against the global availability. The following image shows a sample for the availability metric with a location selected. As you can see, the agent's data is charted in a green line, whereas the global data is charted as an area.
The detailed metrics area shows a tabular view of by-location metrics for each of the locations used in the test. This includes location name, date and time that the data was captured, destination server IP, HTTP response code, number of redirects, and error type/details, if applicable. When a location is selected, it is highlighted in the detailed metrics list.
Response Time
Also known as time-to-first-byte, this is the time elapsed from the beginning of the request (before DNS request) until the client receives the first byte of the response from the server.
Without a Location Selected
The computed averages area shows the response time from the selected agent, and a pie chart breaking down the response timing into DNS lookup connect, wait, and SSL negotiation times. If you hover over the chart, individual timing averages are displayed.
Without a location selected, the timeline shows a chart with the response time calculated from all locations globally. The following image shows an example of a timeline for the response time metric:
Detailed metrics show a tabular view of by-location metrics for each of the locations used in the test. This includes location name, date and time that the data was captured, total response time, and the component times broken down by component (DNS time, connect time, SSL time, wait time).
With a Location Selected
The computed averages area shows the response time from the selected agent, and a pie chart breaking down the response timing into DNS lookup connect, wait, and SSL negotiation times. If you hover over the chart, individual timing is displayed
With a location selected, the timeline shows a chart showing response time for that location, charted against the global average. The following image shows a sample for the response time metric with a location selected. As you can see, the agents data is charted in a blue line, whereas the global data is charted as an area. Where a red line appears, this is an indication that the request timed out for the selected agent.
Detailed metrics will be the same as shown in the global view, showing a tabular view of by-location metrics for each of the locations used in the test. This includes location name, date and time that the data was captured, total response time, and the component times broken down by component (DNS time, connect time, SSL time, wait time). If an agent is selected, the selected location is highlighted.
Throughput
Throughput is the total wire size divided by the receive.
In order to calculate the throughput, Receive Time needs to be >= 1 ms.
Without a Location Selected
The computed averages area shows the average throughput (calculated globally), and a pie chart breaking down the fetch time into DNS lookup, connect, wait, SSL negotiation, and receive times. If you hover over a component of the pie chart, individual component timing is displayed.
In addition to the throughput and the fetch time, the wire size - which is the total size of the object in the wire - is also shown.
With a Location Selected
The computed averages area shows the average throughput (calculated for the location), and a pie chart breaking down the fetch time into DNS lookup, connect, wait, SSL negotiation, and receive times. If you hover over a component of the pie chart, the individual component timing is displayed.
In addition to the throughput and the fetch time, the wire size - which is the total size of the object in the wire - is also shown.
With a location selected, the timeline shows a chart showing throughput for that location, charted against the global average. The following image shows a sample for the throughput metric with a location selected. As you can see, the agent's data is charted in a blue line, whereas the global data is charted as an area.
Detailed metrics will be the same as shown in the global view, showing a tabular view of by-location metrics for each of the locations used in the test. This includes location name, date and time that the data was captured, throughput, wire size, and the component times broken down by component (DNS time, connect time, SSL time, wait time, receive time). The wire size is calculated and is shown as well. If an agent is selected, the selected location is highlighted.
Last updated
