Often used in chats, financial tickers, and gaming applications, Web Sockets allow for simultaneous real-time communication between client and server through a single persistent connection. With the Catchpoint Web Socket Test you can monitor Web Sockets by establishing a connection, sending data, asserting the server response, and creating custom metrics based on the response.
Web Socket Test Properties | |
|---|---|
| Name | A name used to identify this test. |
| Description | Optional additional information about the test |
| Script | The instructions that the agent will execute to run the test. |
| Location | The Product/Folder location of this test (read only) |
| Status | Determines whether this test is current Active or Inactive |
Supported Metrics | |
|---|---|
| % 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/ |
| Client Time (ms) | The total amount of time where no request was on wire, from the start of the test or step to Document Complete. |
| 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. |
| Downloaded Bytes | The total number of downloaded bytes from the primary URL of the test(s). |
| 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. |
| Receive Data Bytes | The total size of data received in bytes. |
| 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. |
| Send Data Bytes | The total size of data sent in bytes. |
| 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) |
| 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. |
| Throughput | Measures how efficiently the system was able to retrieve all elements in kilobytes per second. Throughput is calculated as follows: Throughput = Size / Time where: Size = (FileSize + HeaderSize)/1024 *converts from bytes to KBs Time = (Wait + Load)/1000 *converts from ms to seconds |