inactive
67
edits
IP module: Difference between revisions
Jump to navigation
Jump to search
→TCP statistics
| Line 325: | Line 325: | ||
The graphs below show the historical data for each TCP handshake. The data point is the average handshake time and the vertical line shows the min and max handshake time for that specific time window (depending on the zoom level). Up to two graphs might be visible, one for data when the IP connected other IPs as a client, and another graph for data when the IP has been connected from other IPs as a server. | The graphs below show the historical data for each TCP handshake. The data point is the average handshake time and the vertical line shows the min and max handshake time for that specific time window (depending on the zoom level). Up to two graphs might be visible, one for data when the IP connected other IPs as a client, and another graph for data when the IP has been connected from other IPs as a server. | ||
The TCP application times show info about data packets being transferred between the clients and server. | |||
For each TCP connection, the following key attributes are measured and reported: | |||
* '''Transactions:''' This metric indicates the count of data transaction cycles, allowing you to track the volume of activity over time. | |||
* '''Data Transfer Time:''' This measures the time interval from the first data packet to the last consecutive data packet sent from the same side, giving you a clear picture of the data flow duration. | |||
* '''First Data Response Time:''' This tracks the time between the last data packet sent and the first data packet received from the other peer, marking the conclusion of a transaction cycle | |||
* '''Total Request-Response Time:''' This attribute captures the time interval from the first client data packet to the last server data packet during the entire request-response cycle, offering a comprehensive view of transaction latency. | |||
It’s essential to understand that the values provided by the TCP Application Times feature are correlated through TCP packets containing data. This analysis is performed without decrypting the packets themselves, relying on observed patterns rather than the actual content of the packets. As such, the reported metrics are considered '''heuristics'''—meaning they offer insights based on empirical data rather than direct measurements of specific transactions. This approach allows for efficient monitoring while maintaining data integrity and privacy. | |||
The connection table below shows a subset of the main connection table only for TCP connections for this IP. When sorting the handshake and response time columns and more than one time value is shown in a field, the maximum of all time values of that field is taken into account. | The connection table below shows a subset of the main connection table only for TCP connections for this IP. When sorting the handshake and response time columns and more than one time value is shown in a field, the maximum of all time values of that field is taken into account. | ||