Using the HTTP Server View
Last updated
Last updated
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.
This example shows the result of an HTTP Server test:
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.
To show average availability, response time, or throughput for any single agent charted against the global average of the same metric, select Agents from the Overlay options above the timeline and select the agent. Deselect any agents you have selected from the Agents filter at the top.
Alternatively, you can also show the average availability, response time, or throughput for any agent charted against the average from multiple selected agents. Select the agents you'd like to average from the Agents filter at the top of the timeline screen and then select Agents from the Overlay options. Select the agent you'd like to compare against the group average.
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%.
Multiple Agents View
When no agent is selected or when multiple agents are 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 an agent selected, the timeline shows a chart showing the average availability calculated from all agents globally. If more than one agent is selected, the chart shows the average availability calculated from all selected agents. The following image shows an example of a timeline for the availability metric where no agents are selected:
The table view shows by-agent metrics for each of agents used in the test. This includes agent name, destination server url and IP, date and time that the data was captured, HTTP response code, redirect time, and error type/details, if applicable.
Single Agent View
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 Details, a side panel shows TLS session information as well as request and/or response headers:
With an agent selected, the timeline shows a chart showing average availability for that agent. You can also select the agent from the Overlay options to compare it with the average availability from multiple agents. See Using Timeline Overlays.
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.
Multiple Agents View
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.
The timeline shows a chart with the response time calculated from all agents globally. The following image shows an example of a timeline for the response time metric:
Detailed metrics show a tabular view of by-agent metrics for each of the agents used in the test. This includes agent name, destination server url and IP, 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).
Single Agent View
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 an agent selected, the timeline shows a chart showing average response time for that agent. You can also select the agent from the Overlay options to compare it with the average response time from multiple agents. See Using Timeline Overlays.
Throughput is the total wire size divided by the receive.
In order to calculate the throughput, Receive Time needs to be >= 1 ms.
Multiple Agents View
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.
The timeline shows a chart with the throughput calculated from all agents globally. The following image shows an example of a timeline for the throughput metric:
Detailed metrics show a tabular view of by-agent metrics for each of the agents used in the test. This includes agent name, destination server url and IP, 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, and total time).
Single Agent View
The computed averages area shows the average throughput, calculated for the agent, 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 an agent selected, the timeline shows a chart showing average throughput for that agent. You can also select the agent from the Overlay options to compare it with the average throughput from multiple agents. See Using Timeline Overlays.
