> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/viewing-data/using-the-ftp-server-view.md). # Using the FTP Server View FTP server tests monitor the availability and performance of FTP, FTPS, or SFTP servers by measuring file transfer operations, for example, uploads, downloads, and directory listings. When you create an FTP server test, you get access to the FTP server view. The **Views** available for these tests, accessed via **Network & App Synthetics > Views**, provide different perspectives to analyze test results, presenting metrics such as Availability, Throughput, and Total Time. The FTP server view uses the [ThousandEyes standard layout](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/viewing-data/). ## Example of the FTP Server View This example shows the result of an FTP server download test to server ftp.ripe.net. ![Example of the FTP server view](/files/-M5xtOPtJDS6ocRItB_z) ## Metrics for FTP Server Tests ### Metrics Plottable on the Timeline for FTP Server Tests The timeline displays time-series data as line graphs, suitable for tracking trends over a selected time range. * **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 the DNS request) until the agent receives the first byte of the response from the server. * **Throughput** - The wire size divided by the receive time, expressed in megabits per second (Mb/s). For more details on available metrics, see [this article on ThousandEyes metrics](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/tests/thousandeyes-metrics-what-do-your-results-mean). ### Overlays for FTP Server Tests Overlays facilitate comparative analysis by visualizing how availability, response time, and throughput trend over time, with the ability to highlight specific agents to identify regional or agent-specific issues. Highlighting specific agents isolates performance variations, aiding in pinpointing regional or agent-specific problems. ## View Details for FTP Server Tests The FTP server view shows different data views, depending on whether a specific agent is selected. ### Availability for FTP Server Tests The availability for a given agent is 100% if the FTP reply code is either 2xx or the code specified in the **Desired Reply Code** setting, and 0% otherwise. The average availability can take any value from 0% to 100%. * **Without a Location Selected** The map shows a breakdown by error type, and shows any active alerts. ![Map showing a breakdown by error type without a location selected](/files/-M5xtOPxTEzdY5F1b21k) * **With a Location Selected** The map shows the FTP reply code or similar status, along with a green or red square icon, and any active alerts. ![Map showing the FTP reply code with a location selected](/files/-M5xtOQ0AutlhpHONcNa) Definitions of the possible error types are in the following table: | 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) | | Negotiation | Failure after connect, up to the time the upload/download/list command is issued (including login failure) | | Transfer | Failure during the upload/download/list command execution | | FTP | Receiving an FTP reply code that is not 2XX (default), or not the code configured in **Desired Reply Code** for the test (in Test Settings the field may appear as **Desired status code**) | | Content | Failure to match returned content to an expression in the **Verify content** field | With or without an agent selected, the timeline displays a graph of average availability. With an agent selected, that agent's availability data is plotted in addition to the average availability. The following image shows the availability metric with the Johannesburg agent selected. The agent's data is plotted using a green line, whereas the average availability data is plotted as a solid green area. The data round selector, indicated with the inverted yellow triangle at the top of the selector, is placed on a data round where the Johannesburg agent has 100% availability but the average availability is 80% due to one of the other four agents failing to successfully download the target file. ![Timeline displaying a graph of average availability](/files/-M5xtOQ2k5zKe3CjYKUq) The table shows information for each of the agents used in the test. This includes agent name, date and time that the data was captured, target IP address, FTP error type, and error details (if applicable). In the following image, we see that the 80% average availability displayed in the previous image was due to the Maidenhead, UK agent reaching the test timeout before completing the download. When you select an agent, the agent's row is highlighted in the table. In the image below, the Johannesburg agent has been selected. ![Table showing information for each of the agents used in the test](/files/-M5xtOQ3cR7vpNf1UW_m) ### Response Time for FTP Server Tests Also known as time-to-first-byte, response time is the time elapsed from the beginning of the request (before the DNS request) until the client receives the first byte of the response from the server. The response time metric is accompanied by the individual timings that make up response time. * **Without a Location Selected** The map shows the computed averages area, which contains the response time and throughput averages from all agents that completed the test, and a pie chart breaking down the response into DNS lookup, connect, negotiation, and wait times. If you hover over the chart slices, tooltips show the individual timing averages via tooltips. ![Map showing the computed averages area for response time without a location selected](/files/-M5xtOQ5YPmP6PZ1HRCJ) * **With a Location Selected** The map shows the computed averages area, which contains the response time and throughput from the selected agent if it has completed the test, and a pie chart breaking down the response into DNS lookup, connect, negotiation, and wait times. If you hover over the chart slices, tooltips show the individual timings. ![Map showing the computed averages area for response time with a location selected](/files/-M5xtOQ7jTC3419SrJEA) With or without an agent selected, the timeline displays a graph of average response time. With an agent selected, that agent's response time data is plotted in addition to the average response time. The following image shows the response time metric with the Bruges agent selected. The agent's data is plotted using a blue line, whereas the average response time data is plotted as a solid blue area. ![Timeline displaying a graph of average response time](/files/-M5xtOQ9qyRzTelX-9IR) The table shows information for each of the agents used in the test. This includes agent name, date and time that the data was captured, total response time, and the components of response time: DNS time, connect time, SSL time, and wait time. When you select an agent, the agent's row is highlighted in the table. In the image below, no agent has been selected. ![Table showing response time information for each of the agents](/files/-M5xtOQCel8H8WVgM8cM) ### Throughput for FTP Server Tests Throughput is the total wire size divided by the receive time. The throughput metric is accompanied by the detailed component timings. {% hint style="info" %} In order to calculate the throughput, **Receive Time** needs to be >= 1 ms. {% endhint %} * **Without a location selected** The map shows the computed averages area, which contains the response time and throughput averages from all agents that completed the test, and a pie chart breaking down the throughput into DNS lookup, connect, negotiation, wait, and transfer times. If you hover over the chart slices, tooltips show the individual timing averages. ![Map showing the computed averages area for throughput without a location selected](/files/-M5xtOQDthsZO6RUd3KJ) * **With a Location Selected** The map shows the computed averages area, which contains the response time and throughput from the selected agent if it completed the test, and timing averages via tooltips. ![Map showing the computed averages area for throughput with a location selected](/files/-M5xtOQFRFBXVHAXcTVe) With or without an agent selected, the timeline displays a graph of average throughput. With an agent selected, that agent's throughput data is plotted in addition to the average throughput. The following image shows the throughput metric with the Bruges agent selected. The agent's data is plotted using a blue line, whereas the average throughput data is plotted as a solid blue area. ![Timeline displaying a graph of average throughput](/files/-M5xtOQH_5utS63UTX0O) The **Table** tab shows information for each of the agents used in the test. This includes agent name, date and time that the data was captured, total throughput, and the detailed timings: DNS time, connect time, negotiation time, wait time, transfer time, and total time. When you select an agent, the agent's row is highlighted in the table. In the image below, the Bruges agent has been selected. ![Table showing throughput information for each of the agents](/files/-M5xtOQJhKxpoclUIT9G)