Metric | Description |
Outbound Utilization | The percent utilization of bandwidth configured for the associated Host Group in the outbound direction. |
Inbound Utilization | The percent utilization of bandwidth configured for the associated Host Group in the inbound direction. |
Active Connections | The number of TCP connections that exchanged data in the applicable time interval. TCP connections that were open but did not exchange data are not counted. |
Connection Request Rate | The rate at which TCP SYNs were seen in the applicable time interval. |
Connection Requests | The number of TCP SYNs, excluding any retransmitted SYNs, that were seen in the applicable time interval. |
Connection Setup Time | The time it took for the TCP three-way handshake (connection open) to complete. |
Data Transfer Time | The average time required to successfully transfer client-to-server Request and server-to-client Response data segments that were seen in the applicable time interval. |
Response Data Transfer Time | The average time required to successfully transfer all server-to-client Response data segments that were seen in the applicable time interval. |
Request Data Transfer Time | The average time required to successfully transfer all client-to-server Request data segments that were seen in the applicable time interval. |
Server Hostname | The DNS-resolved name of the TCP server host. |
Client Hostname | The DNS-resolved name of the TCP client host. |
Connections Failed Rate | The rate at which the system saw TCP connections that did not successfully complete the three-way handshake (connection open), e.g., it saw SYNs, but did not see the corresponding/expected SYN-ACKs. |
Connections Failed | The number of TCP connections that did not successfully complete the three-way handshake (connection open) , e.g., the system saw SYNs, but did not see the corresponding/expected SYN-ACKs. Number of SYNs – Connections established. |
Server IP Address | The IP address of the TCP server host. |
Client IP Address | The IP address of the TCP client host. |
Connections Opened | The number of established TCP connections, independent of the number of successful three-way handshakes seen. |
Connections Opened Rate | The rate at which the system saw TCP connections that successfully completed the three-way handshake (connection open). |
Traffic Per Request | The average number of bytes that were carried in the client-to-server Requests that were seen in the applicable time interval. Byte counts are based on powers of 10, not powers of 2, e.g., 1 kB is 1,000 bytes, not 1,024 bytes. |
Traffic Per Response | The average number of bytes that were carried in server-to-client Responses that were seen in the applicable time interval. Byte counts are based on powers of 10, not powers of 2, e.g., 1 kB is 1,000 bytes, not 1,024 bytes. |
Packets Per Request | The average number of packets that were required to successfully transfer a contiguous chunk of client-to-server Request bytes. This is an indication of how big client-to-server Requests were. This includes non-payload control packets such as SYN, ACK, FIN, RST, keep alives, etc. |
Packets Per Response | The average number of packets that were required to successfully transfer a contiguous chunk of server-to-client Response bytes. This is an indication of how big server-to-client Requests were. This includes non-payload control packets such as SYN, ACK, FIN, RST, keep alives, etc. |
Payload Transfer Time | The sum of the average Request and average Response Payload Transfer Times that were measured in the applicable time interval. |
Request Payload Transfer Time | The average estimate of the time it would have taken to successfully transfer a contiguous chunk of Request bytes if there were no retransmissions. In other words, the time taken up by retransmissions, if present, is not accounted for in this metric. |
Response Payload Transfer Time | The average estimate of the time it would have taken to successfully transfer a contiguous chunk of Response bytes if there were no retransmissions. In other words, the time taken up by retransmissions, if present, is not accounted for in this metric. |
Server Reset Rate | The rate at which server-to-client RSTs were seen in the applicable time interval. |
Server TCP Resets | The number of server-to-client RSTs that were seen in the applicable time interval. |
Client TCP Resets | The number of client-to-server RSTs that were seen in the applicable time interval. |
Client Reset Rate | The rate at which client-to-server RSTs were seen in the applicable time interval. |
Reset Rate | The sum of the average rates of client-to-server and server-to-client RSTs that were seen in the applicable time interval. |
Resets | The sum of the number of client-to-server and server-to-client RSTs that were seen in the applicable time interval. |
Response Retrans Delay | An estimate of the average additional time that retransmissions contributed to the successful transfer of server-to-client Responses. |
Request Retrans Delay | An estimate of the average additional time that retransmissions contributed to the successful transfer of client-to-server Requests. |
Retrans Delay | The sum of the average additional times that retransmissions of client-to-server Requests and server-to-client Responses contributed to the successful transfer of those Request and Responses. |
% Retrans | The ratio of all retransmission segments seen to the total number of client-to-server and server-to-client segments that were seen. |
% Response Retrans | The ratio of retransmitted segments to the total number of segments that were seen in the server-to-client direction. |
% Request Retrans | The ratio of retransmitted segments to the total number of segments that were seen in the client-to-server direction. |
Response Retrans Traffic | The number of server-to-client bytes that were retransmitted in the applicable time interval. Byte counts are based on powers of 10, not powers of 2, e.g., 1 kB is 1,000 bytes, not 1,024 bytes. |
Retrans Traffic | The sum of the server-to-client and client-to-server bytes that were retransmitted in the applicable time interval. Byte counts are based on powers of 10, not powers of 2, e.g., 1 kB is 1,000 bytes, not 1,024 bytes. |
Request Retrans Throughput | The rate, in bits per second, required to transmit all the client-to-server Request bytes that were retransmitted. |
Response Retrans Throughput | The rate, in bits per second, required to transmit all server-to-client Response bytes that were retransmitted. |
Retrans Throughput | The rate, in bits per second, of the sum of the client-to-server and server-to-client bytes that were retransmitted. |
Request Retrans Traffic | The client-to-server Request bytes that were retransmitted. |
Response Retrans | The percentage of server-to-client Response packets retransmitted relative to the total number of packets used to transmit the Response. |
Retrans | The percentage of total Request and Response packets retransmitted relative to the total number of packets used to transmit the Request and Response. |
Request Retrans Rate | The rate, in packets per second, of the packets retransmitted for the Request from client-to-server. This includes non-payload control packets such as SYN, ACK, FIN, RST, keep alives, etc. |
Response Retrans Rate | The rate, in packets per second, of the packets retransmitted for the Response from the server-to-client. This includes non-payload control packets such as SYN, ACK, FIN, RST, keep alives, etc. |
Retrans Rate | The rate, in packets per second, of the total packets retransmitted for the Request and Response. This includes non-payload control packets such as SYN, ACK, FIN, RST, keep alives, etc. |
Request Retrans | The percentage of client-to-server Request packets retransmitted relative to the total number of packets used to transmit the Request. |
Round Trip Time | This metric is an estimate of how quickly the network between the client and server would transport bits in both directions if the client and server were infinitely fast, and took no time to respond to Responses and Requests. As of AppResponse 11 Version 11.10.0, Round Trip Time (RTT) comprises two distinct metrics: RTT (self) and RTT (others). RTT (self) is the round trip time as the traffic passes the AppResponse 11 system both from and to the originating IP address or host group. (This is similar to the RTT inbound metric that was used in AppResponse 9.) RTT (others) is the round trip time from when the traffic passes the AppResponse 11 system to when it arrives at another network element, such as an IP address or host group. (This is similar to the RTT outbound metric that was used in AppResponse 9.) RTT, undifferentiated as either (self) or (others), is the sum of the two constituent RTTs: RTT = RTT (self) + RTT (others). See
Round Trip Time for an illustration. |
Server Response Time | An estimate of the average amount of time TCP servers took to send Responses to the immediately preceding client-to-server Requests they received. This is an approximate and directional measure of how much time the server takes to perform data processing before it has data to send back to the TCP clients it is communicating with. |
Server Turn Rate | The per second rate at which Server Turns were seen at the TCP servers that communicated with TCP clients in the applicable time interval. |
Server Turns | The number of data direction turns that were seen at the TCP servers in the applicable time interval. A "data direction turn" is when a Request seen in one direction is immediately followed by a Response from the server in the other direction. (It is common for a Request/Response to be transferred by TCP using multiple TCP segements/packets.) |
User Response Time | The overall responsiveness that the application/process experiences in its use of TCP to transfer and process the Requests and Responses that the application/process created. This metric is calculated as the sum of: (a) The amount of time it took to setup the TCP connections that map to the selected group/object (Connection Setup Time); (b) The amount of time it took to transfer all the Request bytes from client to server ignoring delays due to any retransmissions (Request Payload Transfer Time); (c) The amount of time it took to transfer all the Response bytes from server to client ignoring delays due to any retransmissions (Response Payload Transfer Time); (d) The amount of (processing) time it took the server to send responses to the requests it received from the client (Server Response Time); and (d) The amount of time taken up by retransmissions, if any (Retransmission Delay). |
Packet Traffic | The total number of packets that were seen by the system in both the outbound and inbound directions for the selected group/object. This includes non-payload control packets such as SYN, ACK, FIN, RST, keep alives, etc. |
Outbound Packet Throughput | The total per second packet rate of the packets that were sent by the individual IP hosts in the selected group/object to other individual IP hosts in other groups/objects. This includes non-payload control packets such as SYN, ACK, FIN, RST, keep alives, etc. |
Inbound Packet Throughput | The total per second packet rate of the packets that were received by the individual IP hosts in the selected group/object from other individual IP hosts in other groups/objects. This includes non-payload control packets such as SYN, ACK, FIN, RST, keep alives, etc. |
Outbound Packet Traffic | The total number of packets sent by the individual IP hosts in the selected groups/objects to IP hosts in other groups/objects. This includes non-payload control packets such as SYN, ACK, FIN, RST, keep alives, etc. |
Packet Throughput | The total per second packet rate that was seen by the system in both the inbound and outbound directions involving the individual IP hosts in the selected group/object. This includes non-payload control packets such as SYN, ACK, FIN, RST, keep alives, etc. |
Inbound Packet Traffic | The total number of packets received by the individual IP hosts in the selected group/object's from the IP hosts in other groups/objects. This includes non-payload control packets such as SYN, ACK, FIN, RST, keep alives, etc. |
Outbound Throughput | The per second bit rate of the bytes sent by the individual IP hosts in the selected group/object's to IP hosts in other groups/objects. |
Inbound Throughput | The per second bit rate of the bytes received by the individual IP hosts in the selected group/object's to IP hosts in other groups/objects. |
Inbound Traffic | The total number of bytes that were received by the individual IP hosts in the selected group/object's to IP hosts in other groups/objects. Byte counts are based on powers of 10, not powers of 2, e.g., 1 kB is 1,000 bytes, not 1,024 bytes. |
Outbound Traffic | The total number of bytes that were sent by the individual IP hosts in the selected group/object's to IP hosts in other groups/objects. Byte counts are based on powers of 10, not powers of 2, e.g., 1 kB is 1,000 bytes, not 1,024 bytes. |
Throughput | The total per second bit rate that was seen by the system in both the inbound and outbound directions for the selected group/object. |
Traffic | The total number of bytes that were seen by the system in both the outbound and inbound directions for the selected group/object. Byte counts are based on powers of 10, not powers of 2, e.g., 1 kB is 1,000 bytes, not 1,024 bytes. |
Control Retrans | The number of control packets being retransmitted. |
Control Retrans Rate | The rate of control packets being retransmitted. |
% Control Retrans | The percentage of control packets that were retransmitted (SYN, SYN-ACK). This is 100 * (number of retrans control packets) / (number of total control packets), where total control packets are the control packets plus the retrans control packets. |
Control Packets | The number of control packets (SYNs, SYN ACKs). |
Control Packet Rate | The rate of control packets (SYNs, SYN ACKs). |
Out-of-Order TCP Segments | The percentage of total Request and Response packets received out of order relative to the total number of packets used to transmit the Request and Response. |
Out-of-Order TCP Client Segments | The percentage of client-to-server Request packets received out of order relative to the total number of packets used to transmit the Request. |
Out-of-Order TCP Server Segments | The percentage of server-to-client Response packets received out of order relative to the total number of packets used to transmit the Response. |
Out-of-Order TCP Segment Rate | The rate, in packets per second, of the total packets received out of order for the Request and Response. |
Out-of-Order TCP Client Segment Rate | The rate, in packets per second, of the packets received out of order for the Request from client-to-server. |
Out-of-Order TCP Server Segment Rate | The rate, in packets per second, of the packets received out of order for the Response from the server-to-client. |
Out-of-Order TCP Traffic | The sum of the server-to-client and client-to-server bytes that were received out of order in the applicable time interval. Byte counts are based on powers of 10, not powers of 2, e.g., 1 kB is 1,000 bytes, not 1,024 bytes. |
Out-of-Order TCP Client Traffic | The number of client-to-server bytes that were received out of order in the applicable time interval. Byte counts are based on powers of 10, not powers of 2, e.g., 1 kB is 1,000 bytes, not 1,024 bytes. |
Out-of-Order TCP Server Traffic | The number of server-to-client bytes that were received out of order in the applicable time interval. Byte counts are based on powers of 10, not powers of 2, e.g., 1 kB is 1,000 bytes, not 1,024 bytes. |
Out-of-Order TCP Throughput | The rate, in bits per second, of the sum of the client-to-server and server-to-client bytes that were received out of order. |
Out-of-Order TCP Client Throughput | The rate, in bits per second, required to transmit all client-to-server Request bytes that were received out of order. |
Out-of-Order TCP Server Throughput | The rate, in bits per second, required to transmit all server-to-client Response bytes that were received out of order. |
Client TCP Receive Window | The client-to-server TCP Window value that were seen in the applicable time interval. |
Server TCP Receive Window | The server-to-client TCP Window value that were seen in the applicable time interval. |
Zero Window TCP Segments | The sum of the number of client-to-server and server-to-client Zero Window segments that were seen in the applicable time interval. |
Zero Window TCP Client Segments | The number of client-to-server Zero Window segments that were seen in the applicable time interval. |
Zero Window TCP Server Segments | The number of server-to-client Zero Window segments that were seen in the applicable time interval. |
Zero Window TCP Segment Rate | The sum of the average rates of client-to-server and server-to-client Zero Window segments that were seen in the applicable time interval. |
Zero Window TCP Client Segment Rate | The rate at which client-to-server Zero Window segments were seen in the applicable time interval. |
Zero Window TCP Server Segment Rate | The rate at which server-to-client Zero Window segments were seen in the applicable time interval. |
Metric | Description |
Transaction Metrics | |
Published App/Desktop | Application name (derived from the process, example: Firefox). |
Citrix Client | End user host address (DNS name if resolved, else IP). |
Citrix Client Country | Country name associated with the client IP (example: “United States of America”). |
Citrix Client Host Group IDs | Host Group IDs associated with the end user IP. |
Citrix Client Host Groups | Host Groups associated with the end user IP. |
Citrix Client Hosts | Number of end user IPs associated with current Citrix session. |
Citrix Client IP | End user IP. |
Citrix Client Region | Region name associated with the end user IP (example: “Maryland”). |
Citrix Server | Citrix server host address (DNS name if resolved, else IP). |
Citrix Server Country | Country name associated with the server IP (example: “United States of America”). |
Citrix Server Host Group IDs | Host Group IDs associated with the Citrix Server IP. |
Citrix Server Host Groups | Host Groups associated with the Citrix Server IP. |
Citrix Server IP | Citrix Server IP actively being used. |
Citrix Server Region | Region name associated with the server IP (example: “Maryland”). |
Citrix Servers | Number of Citrix Server IPs associated with current Citrix session. |
Citrix Session Duration | Citrix session duration. It is computed by subtracting the end time from the start time. |
Citrix Session End Time | Citrix session end time. |
Citrix Session ID | Citrix session unique ID (computed internally, assigning different IDs when end user sessions move from one host or client IP to another). |
Citrix Session Start Time | Citrix session start time. |
Citrix Sessions Finished | Number of Citrix sessions finished. |
Citrix Sessions Started | Number of Citrix sessions started. |
Unique Citrix Sessions | Number of unique Citrix sessions (computed based on Citrix Session ID). |
ICA/CGP Compression Ratio | This is a bi-directional measurement (Client to Server and Server to Client). The ratio is computed by dividing the total payload bytes sent/received after compression by the total payload bytes sent/received before compression (since the last reboot). Ratio = “ICA/CGP Traffic“ / “ICA/CGP Uncompressed Traffic”. It is an average computed from samples collected on remote agents. |
ICA/CGP Request Compression Ratio | Client (end user) to Server (Citrix Server) ICA/CGP compression ratio. The ratio is computed by dividing the total payload bytes received after compression by the total payload bytes received before compression (since the last reboot). Ratio = “ICA/CGP Request Traffic“ / |
ICA/CGP Uncompressed Request Traffic | Client (end user) to Server (Citrix Server) ICA/CGP uncompressed traffic. It is the total payload bytes received before compression. It is an average computed from samples collected on remote agents. |
ICA/CGP Request Throughput | Client (end user) to Server (Citrix Server) ICA/CGP throughput. It is an average computed from samples collected on remote agents. |
ICA/CGP Request Traffic | Client (end user) to Server (Citrix Server) ICA/CGP traffic. It is the total payload bytes sent after compression. It is an average computed from samples collected on remote agents. |
ICA/CGP Response Compression Ratio | Server (Citrix Server) to Client (end user) ICA/CGP compression ratio. The ratio is computed by dividing the total payload bytes sent after compression by the total payload bytes sent before compression (since the last reboot). Ratio = “ICA/CGP Response Traffic“ / “ICA/CGP Uncompressed Response Traffic”. It is an average computed from samples collected on remote agents. |
ICA/CGP Response Throughput | Server (Citrix Server) to Client (end user) ICA/CGP throughput. It is an average computed from samples collected on remote agents. |
ICA/CGP Response Traffic | Server (Citrix Server) to Client (end user) ICA/CGP traffic. It is the total payload bytes sent after compression. It is an average computed from samples collected on remote agents. |
ICA/CGP Round Trip Time | This is a bi-directional measurement (Client to Server and Server to Client). It is an average computed from samples collected on remote agents. |
ICA/CGP Throughput | This is a bi-directional measurement (Client to Server and Server to Client). It is an average computed from samples collected on remote agents. |
ICA/CGP Traffic | This is a bi-directional measurement (Client to Server and Server to Client). It is the total payload bytes sent/received after compression. It is an average computed from samples collected on remote agents. |
ICA/CGP Uncompressed Response Traffic | Server (Citrix Server) to Client (end user) ICA/CGP uncompressed traffic. It is the total payload bytes sent before compression. It is an average computed from samples collected on remote agents. |
ICA/CGP Uncompressed Traffic | This is a bi-directional measurement (Client to Server and Server to Client). It is the total payload bytes sent/received before compression. It is an average computed from samples collected on remote agents. |
Roll-up Metrics | |
Published App/Desktop | Application name (example: Firefox). |
Citrix Server | Citrix server host address (DNS name if resolved, else IP). |
Citrix Server Country | Country name associated with the server IP (example: “United States of America”). |
Citrix Server Host Group IDs | Host Group IDs associated with the Citrix Server IP. |
Citrix Server Host Groups | Host Groups associated with the Citrix Server IP. |
Citrix Server IP | Citrix Server IP actively being used. |
Citrix Server Region | Region name associated with the server IP (example: “Maryland”). |
Citrix Session Duration | Citrix session duration. It is computed by subtracting the end time from the start time. |
Citrix Sessions Finished | Number of Citrix sessions finished. |
Citrix Sessions Started | Number of Citrix sessions started. |
ICA/CGP Compression Ratio | This is a bi-directional measurement (Client to Server and Server to Client). The ratio is computed by dividing the total payload bytes sent/received after compression by the total payload bytes sent/received before compression (since the last reboot). Ratio = “ICA/CGP Traffic“ / “ICA/CGP Uncompressed Traffic”. It is an average computed from samples collected on remote agents |
ICA/CGP Request Compression Ratio | Client (end user) to Server (Citrix Server) ICA/CGP compression ratio. The ratio is computed by dividing the total payload bytes received after compression by the total payload bytes received before compression (since the last reboot). Ratio = “ICA/CGP Request Traffic“ / |
ICA/CGP Uncompressed Request Traffic | Client (end user) to Server (Citrix Server) ICA/CGP uncompressed traffic. It is the total payload bytes received before compression. It is an average computed from samples collected on remote agents. |
ICA/CGP Request Throughput | Client (end user) to Server (Citrix Server) ICA/CGP throughput. It is an average computed from samples collected on remote agents. |
ICA/CGP Request Traffic | Client (end user) to Server (Citrix Server) ICA/CGP traffic. It is the total payload bytes sent after compression. It is an average computed from samples collected on remote agents. |
ICA/CGP Response Compression Ratio | Server (Citrix Server) to Client (end user) ICA/CGP compression ratio. The ratio is computed by dividing the total payload bytes sent after compression by the total payload bytes sent before compression (since the last reboot). Ratio = “ICA/CGP Response Traffic“ / “ICA/CGP Uncompressed Response Traffic”. It is an average computed from samples collected on remote agents. |
ICA/CGP Response Throughput | Server (Citrix Server) to Client (end user) ICA/CGP throughput. It is an average computed from samples collected on remote agents. |
ICA/CGP Response Traffic | Server (Citrix Server) to Client (end user) ICA/CGP traffic. It is the total payload bytes sent after compression. It is an average computed from samples collected on remote agents. |
ICA/CGP Round Trip Time | This is a bi-directional measurement (Client to Server and Server to Client). It is an average computed from samples collected on remote agents. |
ICA/CGP Throughput | This is a bi-directional measurement (Client to Server and Server to Client). It is an average computed from samples collected on remote agents. |
ICA/CGP Traffic | This is a bi-directional measurement (Client to Server and Server to Client). It is the total payload bytes sent/received after compression. It is an average computed from samples collected on remote agents. |
CA/CGP Uncompressed Response Traffic | Server (Citrix Server) to Client (end user) ICA/CGP uncompressed traffic. It is the total payload bytes sent before compression. It is an average computed from samples collected on remote agents. |
IICA/CGP Uncompressed Traffic | This is a bi-directional measurement (Client to Server and Server to Client). It is the total payload bytes sent/received before compression. It is an average computed from samples collected on remote agents. |
Traffic Diagnostics | |
Discarded Connections (Flow Collector) | |
Flows discarded (full queue) | Number of flows discarded because the output queue is full. |
Discarded Connections (Flow Processor) | |
Flows discarded (out of order) | Number of discarded flows that are out of order. |
Flows discarded (exceeding limit) | Number of discarded flows that exceed maximum limit (internal limit based on model). |
Flows discarded (full queue) | Number of flows discarded because the output queue is full. |
Discarded Connections (Correlator) | |
Report connections discarded (late arrival) | Number of agent flows discarded for late arrival. |
Report connections discarded (early arrival) | Number of agent flows discarded for early arrival. |
Report connections discarded (unmatched) | Number of agent flows discarded for being unmatched (we were unable to match the agent flows with the probe flows). |
End-to-end transactional flows discarded | Number of end to end Citrix transaction flows discarded because output queue is full. |
End-to-end summary flows discarded | Number of end to end Citrix roll-up flows because output queue is full. |
Flows discarded (late arrival) | Number of probe flows (from packets) discarded for late arrival. |
Flows discarded (early arrival) | Number of probe flows (from packets) discarded for early arrival. |
Flows discarded (duplicate) | Number of duplicate flows discarded. |
Discarded Connections (Agent Processor) | |
Connections discarded (full queue) | Number of flows discarded because the output queue is full. |
Discarded Connections (Agent Processor) | |
Connections discarded (full queue) | Number of flows discarded because the output queue is full. |
Connections discarded (invalid report) | Number of reports (agent bundles) discarded because the report is not valid (for example an unsupported format). |
Connections discarded (invalid session) | Number of sessions (within reports) discarded because the session is not valid (for example an empty session). |
Connections discarded (invalid) | Number of flows (within sessions) discarded because the connection is not valid (for example a null socket = IP=0, port=0) |
Metric | Description |
DB Sessions Busy (Max) | The maximum number of DB sessions that had some query/response activity over the applicable time period. |
DB Sessions Busy | The average number of DB sessions that had some query/response activity over 1-minute buckets. |
Concurrent DB Sessions (Max) | The maximim number of open DB sessions that were present (regardless of query/response activity) over time. |
Concurrent DB Sessions | The average number of open DB sessions that were present (regardless of query/response activity). |
DB Session Event Duration | The total number of minutes the DB session was active this period. |
DB Sessions Idle (Max) | The maximum number of DB sessions that had non-zero idle time in the applicable time period. |
DB Sessions Idle | The average number of DB sessions that had non-zero idle time over 1-minute buckets. |
DB Instance | The user-configured name of the DB instance associated with the selected group. |
Client Process Name | The name of the process in the workstation/server that represents the user side of a DB session. The availability of this information varies by DB vendor. |
DB Session Busy Time | This is the total time of all DB sessions that were active (meaning that a query was ongoing) over the observation interval. If you have 2 DB sessions, one lasting 2 min. with 1 min. activity, and another lasting 5 min. with 2 min. activity, you will see 3 min. for this value. |
Duration Logged In | This is the total time of all DB sessions that were logged in over the observation interval. If you have 2 DB sessions, one lasting 2 min., and another lasting 5 min., you will see 7 min. for this value. |
DB Sessions Detected After Login | The number of DB sessions for which no login was observed, but that were inferred as being DB sessions. |
DB Session ID | A session ID, usually auto-assigned by DBMS. |
DB Session Idle Time | This is the total time of all DB sessions that were idle (meaning that no query was ongoing), rather than busy over the observation interval. If you have 2 DB sessions, one lasting 2 min. with 1 min. idle, and another lasting 5 min. with 2 min. idle, you will see 3 min. for this value. |
DB Sessions Discarded Due To Shutdown | This is the number of sessions discarded due to an AR11 shutdown, not a DBMS shutdown. When AR11 is shutdown, the sessions that were active before the shutdown are discarded when the AR11 comes back up. |
New DB Session Logins | The number of new DB sessions that were seen in the applicable time interval that had a login sequence in the beginning. |
DB Session Logouts | The number of DB sessions that ended with a detected logout sequence. |
DB Sessions Refused | The number of DB session logins that were unsuccessful because the DBMS refused to create sessions, e.g., because of a bad password. |
DB Sessions Discarded Due To Inactivity | The number of DB sessions that did not have any query activity or a logout sequence and are presumed to have ended. |
DB Sessions Finished | The total number of DB sessions that ended for any reason. This is the sum of DB sessions that ended because of logout, refusal, or inactivity timeout. |
New DB Sessions | The total number of new DB sessions that involved a login sequence and new ones that were detected after a login sequence that was not observed. This is the sum of "New DB Session Logins" and "DB Sessions Detected After Login". |
DB Type | The DB type (e.g., Oracle). |
DB Username | The username that was used to login when creating the DB session. |
Client Username | The user name used to log into the client system (e.g., Windows workstation/laptop), making queries and receiving responses. |
Data Transfer Time (Max) | The maximum time it took to transfer a contiguous chunk of query response data, i.e, from the first row to the last row. This time includes any data transfer time observed at the TCP layer in addition to the processing time it took the DB server to send the full response. This is the maximum transfer time for any given DB query in the group over the observation interval. |
Data Transfer Time | This is the time it took to transfer the data returned in the selected query, including the transfer time for the request, e.g., the UPDATE command. |
Data Transfer Time | This is the average time it took to transfer the data returned in the selected query, including the transfer time for the request, e.g., the UPDATE command. |
Transaction Time | The average of the sums of relevant Data Transfer Time + Server Response Time metric values for all queries relevant to the selected group. This is the average transaction time of a DB query from first byte sent to the last byte received. |
Transaction Time | The sum of relevant Data Transfer Time + Server Response Time metric values for all query instances relevant to the selected query. This is the transaction time of the selected DB query from the first byte sent to the last byte received. |
Transaction Time (Max) | The maximum duration of the query from the request to the last packet of the response message. This is the longest query that has been observed within the group during the observation window. |
Packets Per Response (Max) | The maximum number of packets in any DB response sent by DB servers. This represents the largest DB response in terms of packets. |
Request Packet Rate | The packet rate of DB requests sent to DB servers. |
Packets per Request (Max) | The maximum number of packets in any DB request sent to DB servers. This represents the largest DB request in terms of packets that has been observed in the group. |
Response Packets | The total number of packets sent in the DB response by the DB server for the DB query (this applies to a single DB query, not an aggregate). |
Request Packets | The total number of packets sent in the DB request to the DB server for the DB query (this applies to a single DB query, not an aggregate). |
Packets per Request | The average number of packets in a DB request sent to DB servers. |
Packets per Response | The average number of packets in a DB response sent by DB servers. |
Request Packet Traffic | The total number of packets sent as DB requests to DB servers. |
Response Packet Rate | The packet rate of DB responses sent by DB servers. |
Response Packet Traffic | The total number of packets sent as DB responses by DB servers. |
Finished Query Rate | The rate of DB queries that have been completed in the time interval. |
Queries Finished | The number of DB queries that have been completed in the time interval. |
Queries Started | The number of DB queries that started in the time interval. |
Queries Unfinished | The number of DB queries that are unfinished in the time interval. An unfinished DB query is a DB query has started either before or during the time interval, but has not yet completed at the end of the time interval. |
Query Command | The DB query operation (e.g., SELECT, UPDATE, DROP, etc.) |
Query End Time | The end time of an individual DB query. |
Query Return Code | The DB query return code. For each DB query, the DB server returns a code in the DB response indicating whether the query was successful or not. |
Query Serial Number | The unique query identifier. |
Query Start Time | The start time of an individual query. |
Query Status | The status of a query. The status can be one of "C" (=Completed), "I" (=Indeterminate), "R" (=Rejected). |
Query Text | This is the SQL clause sent to the DB server to perform an operation. |
Repetition Count | The number of times a single DB query repeated within a very short time (<1sec). |
Affected Rows | Total number of rows affected by DB queries, either returned, modified, added or removed. |
Affected Rows per Query | The average number of rows affected by a DB query over all the DB queries, either returned, modified, added, or removed. |
Affected Rows per Query (Max) | The maximum number of rows affected by a DB query over all the DB queries, either returned, modified, added, or removed. This represents the largest number of rows that has been affected by a DB query in the group. |
Affected Rows | The number of rows affected by an individual DB query. |
Server Response Time (Max) | The maximum server response time across all DB queries. This represents the largest server response time experienced by any DB query in the group. |
Server Response Time | The average server response time of DB queries in the group. |
Server Response Time | The server response time experienced by the individual query. |
Response Size (Max) | The maximum number of application bytes in a DB response sent by DB servers. This represents the largest DB response in terms of bytes. |
Response Throughput | The application throughput of DB response traffic sent by DB servers. |
Response Traffic | The number of application bytes sent by the DB Server in an individual DB query. |
Request Traffic | The total number of bytes sent in DB requests sent to DB servers. This adds up the number of bytes from all DB requests in the group. |
Request Size (Max) | The maximum number of application bytes in a DB request sent to a DB server across all DB queries. This represents the largest number of bytes sent in a DB request by any DB query in the group. |
Request Throughput | The application throughput of DB request traffic sent to DB servers. |
Request Size | The average number of application bytes in DB requests sent to DB servers. |
Response Traffic | The total number of application bytes sent in DB responses sent by DB servers. This adds up the number of bytes from all DB responses in the group. |
Response Size | The average number of application bytes in DB responses sent by DB servers. |
Request Traffic | The number of application bytes sent to the DB server in an individual DB query. |
Server Hostname | The DNS-resolved name of the TCP server host. |
Client Hostname | The DNS-resolved name of the TCP client host. |
End Time | The TCP flow end time. |
Server IP Address | The IP address of the TCP server host. |
Client IP Address | The IP address of the TCP client host. |
Server Port | The server TCP port. |
Client Port | The client TCP port. |
Start Time | The TCP flow start time. |
Metric | Description |
Burst Duration | The maximum duration of packet loss burst for a single channel. |
Bursts | The number of occurrences of packet loss burst for the channel. |
Channel Duration | The duration of the RTP channel. |
MOS-CQ (End of Call) | The conversational quality MOS score for the channel. |
MOS-V (End of Call) | The average relative MOS score for the video stream. |
Gap Duration | The maximum duration of no packet loss for a single channel. |
Gaps | The number of occurrences of packet loss gap for the channel. |
Jitter (Min) | The jitter of the single RTP channel for the current interval. |
Jitter (Max) | RTP channel jitter of the current interval |
Jitter | RTP channel jitter of the current interval |
Lost Packets | The number of packets that have never been received for an RTP stream for the current interval. |
Interval MOS-CQ (Min) | The lowest channel conversational quality MOS score for the current interval. |
Interval MOS-CQ | The average channel conversational quality MOS score for the current interval. |
Interval MOS-CQ (Max) | The highest channel conversational quality MOS score for the current interval. |
MOS-CQ (Min) | The minimum cumulative channel conversational quality MOS score. |
MOS-CQ (Max) | The maximum cumulative channel conversational quality MOS score. |
Interval Absolute MOS-V (Min) | The minimum absolute MOS score for the video stream for the current interval. |
Interval Absolute MOS-V (Max) | The maximum absolute MOS score of the video stream for the current interval. |
Interval Absolute MOS-V | The average absolute MOS score of the video stream for the current interval, where the interval is calculated every minute, for the minute. |
Absolute MOS-V (Max) | The maximum cumulative absolute MOS score of the video stream. |
Absolute MOS-V (Min) | The minimum cumulative absolute MOS score of the video stream. |
Interval MOS-V (Min) | The minimum relative MOS score for the video stream for the current interval. |
Interval MOS-V (Max) | The maximum relative MOS score for the video stream for the current interval. |
Interval MOS-V | The average relative MOS score of the video stream for the current interval, where the interval is calculated every minute, for the minute. |
MOS-V (Min) | The minimum cumulative relative MOS score of the video stream. |
MOS-V (Max) | The maximum cumulative relative MOS score of the video stream. |
Packet Traffic | The number of RTP packets in the stream for the current interval. |
Corrected Packets | The maximum cumulative number of stream packets corrected by FEC. |
Discarded Packets | The number of stream packets discarded by the endpoint due to late arrival for the current interval. |
Out Of Sequence Packets | The maximum cumulative number of stream packets arriving out of sequence for the current interval. |
Traffic | The number of RTP bytes in the stream for the current interval. |
Throughput | The rate of RTP traffic, in bits per second. |
Jitter (Min) | The lowest jitter value observed across all channels associated with the call at the time observed. |
MOS-CQ (Max) | The best MOS CQ score observed across all RTP streams associated with this call. |
MOS-V (Max) | The best MOS video score observed across all RTP streams associated with this call. |
Call Duration | The cumulative duration of the call. |
Call Ended Status Value | The numerical value corresponding to the final call status (Canceled, Rejected, Completed or Timeout). |
Status (End of Call) | The text name corresponding to the final call status (Canceled, Rejected, Completed or Timeout). |
MOS-CQ (End of Call) | The worst final cumulative MOS CQ score observed accross all RTP streams associated this call. |
MOS-V (End of Call) | The worst final cumulative MOS video score observed accross all RTP streams associated this call. |
Post Dial Delay | The time delay between dial and call start. |
Jitter (Max) | The highest jitter value observed across all channels associated with the call at the time observed. |
MOS-CQ (Min) | The worst MOS CQ score observed across all RTP streams associated with this call. |
MOS-V (Min) | The worst MOS video score observed across all RTP streams associated with this call. |
Metric | Description |
Client Busy Time | The calculated time spent by the end-user/browser between receiving a HTTP Response and sending a subsequent HTTP Request. This is the gap in time between a bar in the waterfall chart and its adjacent (in time) bar. |
Client Busy Time (Normalized) | The relative amount of overall Page Time that was spent in end-user/browser processing time. This is calculated by comparing total Client/Server/Network Busy Times to each other and applying that relative proportion to overall Page Time. |
Page Count ({user_label}) | The number of Individual Page Views for which the attributes and values matched the definition of Custom Metric 1. |
Page Count ({user_label}) | The number of Individual Page Views for which the attributes and values matched the definition of Custom Metric 2. |
Page Count ({user_label}) | The number of Individual Page Views for which the attributes and values matched the definition of Custom Metric 3. |
Page Count ({user_label}) | The number of Individual Page Views for which the attributes and values matched the definition of Custom Metric 4. |
Page Count ({user_label}) | The number of Individual Page Views for which the attributes and values matched the definition of Custom Metric 5. |
Network Busy Time | The calculated time it took the network to transport HTTP Requests and Responses. This is distinct from the processing times in the end-user/browser and the web server. |
Network Busy Time (Normalized) | The relative amount of overall Page Time that the network spent transporting HTTP Requests and Responses. This is calculated by comparing total Client/Server/Network Busy Times to each other and applying that relative proportion to overall Page Time. |
Objects Requested | The number of HTTP Requests that were seen in the context of an Individual Page or coarser grained aggregate like a Page Family, Advanced Web App, etc. |
Originating Hostname | The DNS-resolved hostname of end-user's/browser's IP address. If there were web proxies involved, this hostname will be different than the IP address that was seen in the L3 IP header of the HTTP packets that were anayzed. |
Web User IP | The IP address of the end-user's/browser's host. If there were web proxies involved, this IP address is usually extracted from X-Forwarded-For headers and will not match the IP address that was seen in the IP header of the HTTP packets that were analyzed. |
Page Family ID | A unique number that is used to internally associate Individual Page Views with the Page Families that were associated with it. This has no practical use for the end-user. |
Page Views | The number of Individual Page Views that were observed for each coarser grained group/object such as Web App, Page Family, Geography, etc. Not available for IPVs. |
Page View Rate | The per-second rate of Individual Page Views that were observed for each coarser grained group/object such as Web App, Page Family, Geography, etc. Not available for IPVs. |
% 1xxs | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Codes were >=100 and <200, used to provide Information such as Continue or Processing. |
% 2xxs | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Codes were >=200 and <300, used to indicate Success, such as OK, Created, Accepted. |
% 304s | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Code was 304, indicating Not Modified. |
% 3xxs (Misc) | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Codes were >=300 and <400, used to indicate miscellaneous status, such as Moved Permanently or Found. |
% 400s | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Codes were >=400 and <500, used to indicate Client Errors, such as Bad Request, Not Authorized, Forbidden, and Not Found. |
% 401s | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Code was 401, indicating Unauthorized. |
% 402s | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Code was 402, indicating Payment Required. |
% 403s | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Code was 403, indicating Forbidden. |
% 404s | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Code was 404, indicating Not Found. |
% 407s | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Code was 407, indicating Proxy Authentication Required. |
% 4xxs (Misc) | Percent of 4xx errors |
% 500s | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Codes were >=500, used to indicate Internal Server Errors, such as Not Implemented, Service Unavailable, and HTTP Version Not Supported. |
% 501s | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Code was 501, indicating Not Implemented. |
% 503s | The percentage of objects associated with a coarser grained group/object for which the HTTP Status Code was 503, indicating Service Unavailable. |
% 5xxs (Misc) | Percent of 5xx errors |
% Slow Pages | The percentage of objects requested that exceeded the Slow Page Threshold value. |
1xxs | The number of objects associated with a coarser grained group/object for which the HTTP Status Codes were >=100 and <200, e.g., used to indicate Continue, Processing. |
2xxs | The number of objects with a status code >= 200 and < 300, used to indicate Success, such as OK, Created, Accepted. |
304s | The number of objects with a status code of 304, indicating Not Modified. |
3xxs (Misc) | The number of objects with a status code >= 300 and < 400 and != 304. |
400s | The number of objects with a status code of 400, indicating Bad Request. |
401s | The number of objects with a status code of 401, indicating Unauthorized. |
402s | The number of objects with a status code of 402, indicating Payment Required. |
403s | The number of objects with a status code of 403, indicating Forbidden. |
404s | The number of objects with a status code of 404, indicating Not Found. |
407s | The number of objects with a status code of 407, indicating Proxy Authentication Required. |
4xxs (Misc) | The number of objects with a status code > 404 and < 500 and != 407. |
500s | The number of objects with a status code of 500, indicating Internal Server Error. |
501s | The number of objects with a status code of 501, indicating Not Implemented. |
503s | The number of objects with a status code of 503, indicating Service Unavailable. |
5xxs | The number of objects with a status code of 500 and greater. |
5xxs (Misc) | The number of objects with a status code of 502 or > 503. |
Server Busy Time | The amount of time it took a web server to start sending HTTP Responses after receiving the corresponding HTTP Requests. This is distinct from the processing times in the end-user/browser and the network. |
Server Busy Time (Normalized) | The relative amount of overall Server Busy Time that the server took to start responding to HTTP Requests. This is calculated by comparing total Client/Server/Network Busy Times to each other and applying that relative proportion to overall Page Time. |
Slow Pages | The number of Individual Page View whose Page Times were greater than the applicable Slow Page Threshold. It is possible for an Individual Page View to be associated with multiple Web Applications and Page Families. If you are looking at this metric for a Web Server IP->Web App group path, the # of slow pages for that Web Server IP may not be the sum of this metric's values for the Web Apps shown for that Web Server IP. |
Slow Page Rate | The number of pages exceeding the Slow Page Threshold value. |
Page Time | The total amount of elapsed time for the end-user/browser to receive HTTP Responses for all the HTTP Requests that constituted an Individual Page View. If an IPV contains a hundred objects, this is the time it took for all those objects to be received by the browser. |
Page Response Traffic | The sum, in bytes, of all HTTP responses (body plus header). |
Page Response Throughput | The average rate, in bytes per second, of all HTTP responses (body plus header). |
Page Request Traffic | The sum, in bytes, of all HTTP requests (body plus header). |
Page Request Size | The average size, in bytes, of all HTTP requests (body plus header). |
Page Size | The average number of bytes that made up all the headers and bodies of the HTTP Requests and Responses that were stitched into Individual Page Views. This is a measure of how many bytes were involved in a single page. |
Page Traffic | The total number of bytes that made up all the headers and bodies of the HTTP Requests and Responses that were stitched into Individual Page Views. This is a measure of how many bytes were involved in all the IPVs associated with the selected group/object. |
Page Response Size | The average size, in bytes, of all HTTP responses (body plus header). |
Page Request Throughput | The average rate, in bytes per second, of all HTTP requests (body plus header). |
Page Throughput | The average rate, in bytes per second, of all HTTP requests and responses (body plus header). |
User ID | An internal ID that is used to map User Names with Individual Page Views. This is not useful to the end-user. |
User | The Username that was derived from applying User Session Tracking rules to the Individual Page View. In most cases, this represents the username who logged in and setup the web sessions that produced all the Individual Pages. |