| Measurement |
Description |
Measurement
Unit |
Interpretation |
| No_of_sessions |
Represents the current number of sessions for a particular user |
Number |
A value of 0 indicates that the user is not currently connected to the
Citrix server. |
| Latency_last |
Represents the
average client latency for the last request from a user. The latency is measured by rhe Citrix server based on packets sent to and from each client during a session - this includes network delay plus server side processingdelays. The value reported is the average of the last latencies for all the current sessions of a user. |
Secs |
This measure will be reported only if the COLLECT EXTENDED METRICS flag is set to ‘Yes’.
|
| Latency_avg |
Represents the
average client latency for a user. The value reported is the average
of the latencies for all the current sessions of a user. |
Secs |
This measure will be reported only if the COLLECT EXTENDED METRICS flag is set to ‘Yes’.
A consistently high latency may be indicative of performance degradations with the Citrix servers. Possible reasons for an increase in latency could be increased network delays, network congestion, Citrix server slow-down, too many simultaneous users on the Citrix server etc. Typically latencies on a Citrix server will be below 5 secs. |
| Latency_devn |
The latency deviation represents the difference between the minimum and maximum measured latency values for a session. The value reported is the average of the latency deviations for all the current sessions of a user. |
Secs |
This measure will be reported only if the COLLECT EXTENDED METRICS flag is set to ‘Yes’.
Ideally, the deviation in latencies over a session should be minimum so as to provide a consistent experience for the user. |
| Mem_util |
This value represents the ratio of the resident set size of the memory utilized by the user to the physical memory of the host system, expressed as a percentage. If a user is connected via multiple sessions, the value
reported is the sum of all memory utilizations across all the
sessions. |
Percent |
This
value indicates the percentage of memory resources that are used up by
a specific user. By comparing this value across users, an
administrator can identify the most heavy users of the Citrix
server. Check the detailed diagnosis to view the offending processes/applications. |
| Cpu_util |
The CPU utilization for a session is the percentage of time that all of the threads/processes of a user session used the processor to execute instructions. If a user is connected via multiple sessions, the value reported is the sum of all CPU utilizations across all the sessions. Also, in multi-processor environments, the average CPU usage per processor is reported as the value of this measure – i.e., if your Citrix server is using an 8-core processor and the total CPU usage of a user across all his/her sessions amounts to 40%, then this measure will report CPU usage as 5 % (40/8 processors = 5). |
Percent |
This measure serves as a good indicator of CPU usage in load-balanced environments, where the user load is balanced across all processors. Excessive CPU usage by a user can impact performance for other users. This is why, a high value for this measure is a cause for concern. In such cases, check the detailed diagnosis to view the offending processes/applications. |
| Input_bandwidth |
Indicates
the average bandwidth used for client to server communications for all
the sessions of a user |
KB/Sec |
|
| Output_bandwidth |
Indicates
the average bandwidth used for server to client communications for all
the sessions of a user |
KB/Sec |
|
| Input_line_speed |
Indicates
the average line speed from the client to the server for all the
sessions of a user |
KB/Sec |
|
| Output_line_speed |
Indicates
the average line speed from the server to the client for all the
sessions of a user |
KB/Sec |
|
| Input_compression |
Indicates
the average compression ratio for client to server traffic for all the
sessions of a user |
Number |
|
| Output_compression |
Indicates
the average compression ratio for server to client traffic for all the
sessions of a user |
Number |
|
| IO_reads |
The rate of I/O reads done by all processes being run by a user |
KBps |
These metrics measure the collective I/O activity (which includes file, network and device I/O's) generated by all the processes being executed by a user. When viewed along with the system I/O metrics reported by the DiskActivityTest, these measures help you determine the network I/O. Comparison across users helps identify the user who is running the most I/O-intensive processes. Check the detailed diagnosis for the offending processes/applications. |
| IO_writes |
The rate of I/O writes done by all processes being run by a user |
KBps |
| Page_faults |
The rate of page faults seen by all processes being run by a user |
Faults/Sec |
Page Faults occur in the threads executing in a process. A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. If the page is on the standby list and hence already in main memory, or if the page is in use by another process with whom the page is shared, then the page fault will not cause the page to be fetched from disk. Excessive page faults could result in decreased performance. Compare values across users to figure out which user is causing most page faults. |
| Handles |
The total number of handles being currently held by all processes of a user. |
Number |
A consistent increase in the handle count over a period of time is indicative of malfunctioning of programs. Compare this value across users to see which user is using a lot of handles. Check detailed diagnosis for further information. |
| Input_audio_bandwidth |
Indicates the bandwidth used while transmitting sound/audio to this user. |
Kbps |
Comparing these values across users will reveal which user is sending/receiving bandwidth-intensive sound/audio files over the ICA channel. To minimize bandwidth consumption, you may want to consider disabling client audio mapping. |
| Output_audio_bandwidth |
Indicates the bandwidth used while receiving sound/audio from this user. |
Kbps |
| Input_com_bandwidth |
Indicates the bandwidth used when sending data to this user's COM port. |
Kbps |
Comparing these values across users will reveal which user's COM port is sending/receiving bandwidth-intensive data over the ICA channel.
This measure will be reported only if the COLLECT EXTENDED METRICS flag is set to ‘Yes’. |
| Output_com_bandwidth |
Indicates the bandwidth used when receiving data from this user's COM port. |
Kbps |
| Input_drive_bandwidth |
Indicates the bandwidth used when this user performs file operations on the mapped drive on the virtual desktop. |
Kbps |
Comparing the values of these measures across users will reveal which user is performing bandwidth-intensive file operations over the ICA channel.If bandwidth consumption is too high, you may want to consider disabling client drive mapping on the client device. Client drive mapping allows users logged on to a virtual desktop from a client device to access their local drives transparently from the ICA session. Alternatively, you can conserve bandwidth by even refraining from accessing large files with client drive mapping over the ICA connection.
This measure will be reported only if the COLLECT EXTENDED METRICS flag is set to ‘Yes’. |
| Output_drive_bandwidth |
Indicates the bandwidth used when the virtual desktop performs file operations on the client's drive. |
Kbps |
| Input_printer_bandwidth |
Indicates the bandwidth used when this user prints to a desktop printer over the ICA channel. |
Kbps |
Comparing the values of these measures across users will reveal which user is issuing bandwidth-intensive print commands over the ICA channel.If bandwidth consumption is too high, you may want to consider disabling printing. Alternatively, you can avoid printing large documents over the ICA connection. |
| Output_printer_bandwidth |
Indicates the bandwidth used when the desktop responds to print jobs issued by this user. |
Kbps |
| Input_session_bandwidth |
Indicates the bandwidth used from this user to the virtual desktop for a session |
Kbps |
Comparing the values of these measures across users will reveal which user and which virtual desktop is performing bandwidth-intensive operatons for a session. |
| Output_session_bandwidth |
Indicates the bandwidth used from the virtual desktop to this user for a session. |
Kbps |
| Input_speedscreen_data_bandwidth |
Indicates the bandwidth used from this user to the virtual desktop for data channel traffic. |
Kbps |
Comparing the values of these measures across users will reveal which user has been transmitting/receiving bandwidth-intensive data channel traffic.
This measure will be reported only if the COLLECT EXTENDED METRICS flag is set to ‘Yes’. |
| Output_speedscreen_data_bandwidth |
Indicates the bandwidth used from virtual desktop to this user for data channel traffic. |
Number |
| Input_speedscreen_multi_bandwidth |
Indicates the bandwidth used from this user to virtual desktop for flash v2 data traffic. |
Kbps |
Comparing the values of these measures across users will reveal which user has been transmitting/receiving bandwidth-intensive flash v2 data.
|
| Output_speedscreen_multi_bandwidth |
Indicates the bandwidth used from the virtual desktop to this user for flash v2 data traffic |
Kbps |
| Input_hdx_bandwidth |
Indicates the bandwidth used from this user to virtual desktop for flash data traffic. |
Kbps |
Comparing the values of these measures across users will reveal which user has been transmitting/receiving bandwidth-intensive flash data. |
| Output_hdx_mediaStream |
Indicates the bandwidth used from the virtual desktop to this user for flash data traffic. |
Kbps |
|
| Input_usb_bandwidth |
Indicates the bandwidth used from this user to virtual desktop by Program Neighborhood to obtain application set details. |
Kbps |
Comparing the values of these measures across users will reveal which user has been transmitting/receiving bandwidth-intensive PN traffic.
These measures will be reported only if the COLLECT EXTENDED METRICS flag is set to ‘Yes’. |
| Output_usb_bandwidth |
Indicates the bandwidth, used from the virtual desktop to this user by Program Neighborhood to obtain application set details. |
Kbps |
| Cpu_util_time |
Indicates the percentage of time, across all processors, this user hogged the CPU. |
Percent |
The CPU usage for user's processes measure indicates the percentage of overall server CPU time that a user is using. For example, if a user is taking up one of the server's CPUs for 100% of the time and there are 8 CPUs on the server, CPU usage for user's processes will be 12.5% (100/800). While 12.5% may seem to be a low number, the fact that the user is taking up one of the CPUs of the server is significant. Hence, CPU time used by user's session measure is a better indicator of CPU usage by users. In the above example, since the user is consuming 100% of one processor, CPU time used by user's session will be 100%. A high value for this measure or a consistent increase in the value of this measure demands attention. Use the detailed diagnosis to know what CPU intensive activities are being performed by the user. |
| Bandwidth_usage |
Indicates the percentage HDX bandwidth consumption of this user. |
Percent |
Compare the value of this measure across users to know which user is consuming the maximum HDX bandwidth. |
| Input_thinwire_bandwidth |
Indicates the bandwidth used from client to server for ThinWire traffic. |
Kbps |
Typically, ICA traffic is comprised of many small packets, as well as a some large packets. Large packets are commonly generated for initial session screen paints and printing jobs, whereas the ongoing user session is principally comprised of many small packets. For the most part, these small packets are the highest priority ICA data called Thinwire. Thinwire incorporates mouse movements and keystrokes.
Compare the value of these measures across users to know which user's keystrokes and mouse movements are generating bandwidth-intensive traffic.
These measures will be reported only if the COLLECT EXTENDED METRICS flag is set to ‘Yes’. |
| Output_thinwire_bandwidth |
Indicates the bandwidth used from server to client for ThinWire traffic. |
Kbps |
| Input_seamless_bandwidth |
Indicates the bandwidth used from client to server for published applications that are not embedded in a session window. |
Kbps |
Compare the value of these measures across users to know which user is accessing bandwidth-intensive applications that are not in a session window.
These measures will be reported only if the COLLECT EXTENDED METRICS flag is set to ‘Yes’. |
| Output_seamless_bandwidth |
Indicates the bandwidth used from server to client for published applications that are not embedded in a session window. |
Kbps |
| Resource_shares |
Indicates the total number of resource shares used by this user. |
Number |
By comparing the value of this measure across users, you can identify the user who is hogging the resources.
This measure will be reported only if the COLLECT EXTENDED METRICS flag is set to ‘Yes’. |
| Total_session_duration |
Indicates the time that has elapsed since this user logged in. |
Mins |
Compare the value of this measure across users to know which user has been logged in for the longest time. |
| Idle_time_measureprd |
Indicates the percentage of time in the last measurement period during which this user actively used the server. |
Percent |
Ideally, the value of this measure should be 100%.
A low value for this measure denotes a high level of inactivity recently. |
| Idle_time_duration |
Indicates the time that has elapsed since this user performed an action on the server. |
Mins |
A high value for this measure indicates that the user has been idle for a long time. Compare the value of this measure across users to know which user has been idle for the longest time. |
| Total_idle_duration |
Indicates the total time for which this user was idle during the session. |
Mins |
If the value of this measure is the same as the value of the Total time in session measure for a user, it means that the user has been idle throughout the session.
If the value of this measure is close to the value of the Total_session_duration measure for a user, it implies that the user has been idle for a long time.
If the value of this measure is much lesser than the value of the Total_session_duration measure for a user, it means that the user has been active for most part of the session. |
| Total_bandwidth |
Indicates the total bandwidth usage of the sessions of this user. |
Kbps |
Compare the value of this measure across users to know which user is consuming the maximum bandwidth. |
| Memory_used |
Indicates the current size of the working set of this user's processes |
MB |
The Working Set is the set of memory pages touched recently by the threads in a process. If free memory in the server is above a threshold, pages are left in the Working Set of a process even if they are not in use.
When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before leaving main memory. If multiple processes are running in the user's session, the memory working set reported is the sum of the working sets for all the user's processes. Comparing the working set across users indicates which user(s) are taking up excessive memory. Check the detailed diagnosis to view the offending processes/applications. |
| Process_count |
Indicates the count of processes running in this user's session. |
Number |
|