The Transport Test monitors the performance and availability of a connection to a given host using the TCP or UDP protocol. Creating a test involves defining the host and port you want Catchpoint to test, and the request data you want Catchpoint to send.
Transport Test Properties | |
|---|---|
| Name | A name used to identify this test. |
| Description | Optional additional information about the test |
| Monitor | The protocol used to test the connection to the host. TCP or UDP. |
| Test Location | The IP Address or hostname, and port number, of the destination host. (hostname:port)
|
| Format | The format of the data the test will post to the destination. Plain Text, HEX, or Base 64 |
| Post Data | The data that the test will post to the destination host. |
| Location | The Product/Folder location of this test (read only) |
| Status | Determines whether this test is currently Active or Inactive |
Supported Metrics | |
|---|---|
| # Purged Runs | The number of test runs manually excluded from calculation for purposes of SLA accuracy. |
| # Runs | Total number of test runs for the defined time period. |
| # Test Errors | The total number of test runs that failed. This is the sum of all of the following types of test failures:
|
| # Test Failures | The total number of elements that Catchpoint was unable to connect to, receive a response from, or load on the page. |
| % Adjusted Availability | Ignoring any purged runs, the percentage of test runs where the primary URL server was reached and the test was completed (i.e. there was not a Test Error.) |
| % Availability | The percentage of test runs where the primary URL server was reached and the test was completed (i.e. there was not a Test Error.) Availability is calculated as: (# Test Runs - # Test Errors) / # Test Runs |
| % Downtime | The percentage of test runs where the primary URL server was unavailable, unreachable, or otherwise failed (i.e. there was a Test Error.) Downtime is calculated as: # Test Errors / # Test Runs |
| % Frustrated | The percentage of test runs that exceeded the Apdex “frustrated” threshold. |
| % Not Frustrated | The percentage of test runs that completed in less time than the Apdex “frustrated” threshold. This is equivalent to: % Satisfied + % Tolerating |
| % Satisfied | The percentage of test runs that completed in less time than the Apdex “Satisfied” threshold. |
| % Tolerating | The percentage of test runs that exceeded the Apdex “Satisfied” threshold but completed in less time than the “Frustrated” threshold. |
| Apdex | A scoring mechanism that translates performance metrics of diverse applications into generic “User Satisfaction” levels using predefined response time thresholds. You can use default Apdex thresholds or configure your own on a per basis. For more details about Apdex, visit http://www.apdex.org/ |
| Connect (ms) | The time it took to establish a TCP connection with the server. |
| DNS (ms) | The time it took to resolve the domain name to an IP address. |
| Download File Size | The size of the downloaded file. |
| Download Throughput | Measures how efficiently the system was able to retrieve the file from the server. This is calculated as: Download File Size / Download (ms) |
| Experience Score | A composite metric that captures the overall experience of a user on a scale of 0-100. |
| Load (ms) | The time from the first packet to the last packet of data for the response. |
| Response (ms) | The total time from the initial request until receiving the last packet of response data. It is the sum of DNS + Connect + ssl + Send + Wait + Load for all elements. |
| Send (ms) | The time it took to send the request to the server. |
| Server Response (ms) | The time from when DNS was resolved to receiving the last response packet from server. (This shows the server response exclusive of dns times) |
| Signal Quality | Measures the quality of the WLAN connection in terms of data transfer speed. It indicates what percent of the available network are you using to move data (upload / download). 99% is as good as it gets in terms of signal quality. |
| Signal Strength (dBm) | This number represents the power the clients device is receiving from the Access Point / Wi-Fi router. A number of -30 dBm indicates excellent while a number of -70dBm indicates very poor signal strength. |
| Test Time (ms) | One cohesive metric that applies to all test types and indicates the total duration of the test run. Test Time is equivalent to Response, Test Response (Transaction and web tests) and ping RTT (Trace Route tests), and is used when calculating Apdex. Test Time is not available for Request, Host, or Zone charting. |
| Time To First Byte (ms) | The total time from the initial DNS request to receiving the first response packet from the server. This is calculated as: |
| Wait (ms) | The time from when the request was sent to the server until the first response packet was received. (Known as "First Byte" in some tools) |