Citrix XA Users Test

A Citrix environment is a shared environment in which multiple users connect to a Citrix server/server farm and access a wide variety of applications. When server resources are shared, excessive resource utilization by a single user could impact the performance for other users. Therefore, continuous monitoring of the activities of each and every user on the server is critical. Towards this end, the Citrix XA Users test assesses the traffic between the user terminal and the server, and also monitors the resources taken up by a user's session on the server. The results of this test can be used in troubleshooting and proactive monitoring. For example, when a user reports a performance problem, an administrator can quickly check the bandwidth usage of the user's session, the CPU/memory/disk usage of this user's session as well as the resource usage of other user sessions. The administrator also has access to details on what processes/applications the user is accessing and their individual resource usage. This information can be used to spot any offending processes/ applications.  

Note:

This test will report metrics only if the XenApp server being monitored uses the .Net framework v3.0 (or above).

Target of the test : Any Citrix server

Agent deploying the test : An internal agent

Outputs of the test :One set of results for every user logged into the Citrix server

Configurable parameters for the test
  1. TEST PERIOD - How often should the test be executed
  2. Host – The host for which the test is to be configured.
  3. Port – Refers to the port used by the Citrix MF XP server. 
  4. Usernames - Specify the name of the user whose performance statistics need to be generated. By default, "all" will be displayed here, indicating that the eG agent, by default, reports statistics pertaining to all users who are currently logged in. Multiple user names can be specified as a comma-separated list. In such cases, the eG agent will report statistics for the users listed in the arguments only.
  5. farmname - If the Citrix server for which this test is being configured belongs to a Citrix farm, then provide the name of the Citrix farm server that controls it, in the FARMNAME text box. While specifying the FARMNAME, ensure that you provide the same name that was specified against the HOST/NICK NAME field while managing the Citrix farm server using the eG Enterprise system. In the event of a name mismatch, eG will be unable to extract the required measures for this test. By default, ‘none’ will be displayed here.
  6. farmport – Specify the port number at which the Citrix farm listens.
  7. appsbyname - By default, this flag is set to No - i.e., the detailed diagnosis for a user reports the process name(s) being run by the user. If this parameter is set to Yes, the agent compares the full process command including arguments with the published application information and reports the process that the user is running plus the application that the user is accessing (e.g., MSWord (sfftray) - in this example, MSWord is the published application name, and sfftray is the Softgrid client executable that is streaming this application from a Softgrid server).
  8. showpublisheddesktops - By default, this flag is set to No. If set to Yes, then the detailed diagnosis of the test, which typically lists the resource-intensive processes/applications accessed by a user, will additionally indicate the exact published desktop that has been used by the user or used to access the application.
  9. report total - By default, this flag is set to No. If set to Yes, then the test will report measures for only a Total descriptor. For this descriptor, the test will report the aggregate resource usage across all users to the Citrix server. The default setting (No) of the flag on the other hand, implies that the test reports a set of metrics for each user to the server, by default.
  10. reportbyclientname - By default, this flag is set to No. If set to Yes, this test will report metrics for each client machine from which users logged into the XenApp server - i.e., the host name of the client machines will be the descriptors of this test. In this case therefore, the User name column of the detailed diagnosis of this test will indicate the names of the users who logged into the XenApp server.

    On the other hand, if the reportbyclientname flag is set to No, then user names will be the descriptors of the test, and the User name column in the detailed diagnosis will display a '-' (hyphen). 

  11. apps rediscover period - By default, the test rediscovers the applications running on a Citrix server, every 15 minutes; this is why, the apps rediscover period is set to 15 by default. You can override this default setting by specifying a different duration (in minutes) in the apps rediscover period text box.
  12. ctxappdisctimerange - Typically, when monitoring a Citrix server/farm on which numerous applications have been deployed, the processing overheads of this test may increase every time the test performs application discovery. You may hence prefer to rediscover the applications on these servers/farms only during such times the user activity/load on the server/farm is low. To schedule application rediscovery during the 'low-activity' time window of a XenApp server, you can use the ctxappdisctimerange parameter. Here, specify a time range in the following format: StartingHrs-Ending Hrs. The Hrs here should be in the 24-hour format.  For instance, to make sure that the test performs application rediscovery only during 8PM and 11PM every day, your ctxappdisctimerange specification will be: 20-23. Note that you cannot suffix your 'Hrs' specification with 'Minutes' or 'Seconds'.

    By default, the ctxappdisctimerange is none; this implies that applications are by default rediscovered only in the frequency specified against apps rediscover period. However, if a valid time range is provided against the ctxappdisctimerange parameter, then this time range will automatically override the apps rediscover period.

  13. separate process - By default, this parameter is set to Auto. This implies that by default, this test auto-discovers the operating system on which the target Citrix server is running. Based on the auto-discovered OS, the test uses either the eG agent process itself to collect the required metrics or spawns a separate process for this purpose. If the target server is discovered to be executing on a Windows 2003 (or earlier) platform, then the eG agent process itself will collect the metrics reported by this test. On the other hand, if the target server is found to execute on Windows 2008 (or above), then a separate process is spawned for metrics collection. Alternatively, you can set this flag to true or yes. In this case, metrics collection is performed by a separate process, regardless of the operating system of the Citrix server. If you set this flag to false or no on the other hand, then the eG agent process collects the metrics, regardless of the operating system of the Citrix server.
  14. domain name, domain user, domain password, and confirm password – A Citrix XenApp server (v6.5) can run in the controller mode or the worker mode. In the controller mode, the XenApp server can perform all farm management tasks. However, in the worker mode, a XenApp server can only host user sessions.

    By default, the domain name, domain user, domain password, and confirm password parameters are set to none. If the XenApp server being monitored is the controller in a farm, then this default value will automatically apply. In other words, in this case, you can leave the values of these parameters as none. On the other hand, if the target XenApp server is a worker in the farm, then first, you will have to configure the name of the domain in which the XenApp server operates in the domain name text box. Then, you need to configure the test with the credentials of a user with Citrix Farm Administrator rights, using the domain user and domain password text boxes. Finally, you will have to confirm the domain password by retyping it in the confirm password text box.

    Note:

    If the XenApp server is a worker in the farm, then, in addition to configuring the domain name, domain user, domain password parameters, the following pre-requisites should also be fulfilled for this test to report metrics:

    • Make sure that the Citrix XenApp Commands Remoting service is running in the Controller server.
    • The port 2513 must be open on the Controller server in the farm.
  15. show worker groups - Worker groups are collections of XenApp servers, residing in the same farm, that are managed as a single unit. You can publish applications to a worker group. If you want to know the worker group to which every application accessed by a user has been published, then set this parameter to Yes. If both the show worker groups and appsbyname flags are set to Yes, the detailed diagnosis of this test will display the worker group name along with the name of the application accessed by the user. By default, this parameter is set to No.
  16. report by domain name – By default, this flag is set to Yes. This implies that by default, this test will report metrics for every domainname\username. This way, administrators will know which user logged in from which domain. If you want the test to report metrics for every username only, then set this flag to No.
  1. enable browser monitoring – By default, this flag is set to No, indicating that the eG agent does not monitor browser activity on the XenApp server. If this flag is set to Yes, then, whenever one/more IE (Internet Explorer) browser instances on the XenApp server are accessed, the detailed diagnosis of the User sessions measure will additionally reveal the URL being accessed via each IE instance and the resources consumed by every URL. Armed with this information, administrators can identify the web sites that are responsible for excessive resource usage by an IE instance.  
  2. collect extended metrics – By default, this parameter is set to No, indicating that the test will report only a standard set of user experience metrics. To enable the test to collect additional metrics per user, set this flag to Yes.
  3. detailed diagnosis - To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability
    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

User 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. 

Use the detailed diagnosis of this measure to know the details of the sessions.

Screen refresh latency - last:

Represents the average client latency for the last request from a user. The latency is measured by the Citrix server based on packets sent to and from each client during a session - this includes network delay plus server side processing delays. The value reported is the average of the last latencies for all the current sessions of a user.

Secs

 

Screen refresh latency - avg:

Indicates the average time interval measured at the client between the first step (user action) and the last step (graphical response displayed) of this user's interactions with the server. The value reported is the average of the latencies for all the current sessions of a user. 

Secs

This is a measurement of the screen lag that a user experiences while interacting with the XenApp server. In other words, is the latency detected from when the user hits a key unti the response is displayed.

Comparing the value of this measure across users will enable administrators to quickly and accurately identify users who are experiencing higher latency when interacting with the XenApp server.

If both the Screen refresh latency and Client network latency measures report high values, it implies that network slowness is contributing to user-perceived Citrix slowness (i.e., the problem is not due to the Citrix servers, but probably due to the network connection that the user is connecting from - e.g., a wireless WAN).

If Screen refresh latency is high and Client network latency is low, this implies that there is a bottleneck in the Citrix stack that is causing user experience to be poor (e.g., overloaded server or virtual platform, slowness in storage, etc.). Slowness can also occur because of client-side processing delays on the receiver end.

Screen refresh latency -deviation:

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

Ideally, the deviation in latencies over a session should be minimum so as to provide a consistent experience for the user.

This measure will be reported only if the collect extended metrics flag is set to ‘Yes’.

Memory usage for user’s processes:

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 usage for user’s processes:

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

 

I/O reads for user's processes:

Indicates 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.    

I/O writes for user’s processes:

Indicates the rate of I/O writes done by all processes being run by a user.

KBps

Page faults for user’s processes:

Indicates 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 used by user’s processes:

Indicates 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. 

Audio bandwidth input:

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.

Audio bandwidth output:

Indicates the bandwidth used while receiving sound/audio from this user.

Kbps

COM bandwidth input:

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’.

COM bandwidth ouput:

Indicates the bandwidth used when receiving data from this user’s COM port.

Kbps

Drive bandwidth input:

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.

These measures will be reported only if the collect extended metrics flag is set to ‘Yes’.

Drive bandwidth output:

Indicates the bandwidth used when the virtual desktop performs file operations on the client’s drive.

Kbps

Printer bandwidth input:

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.

Printer bandwidth output:

Indicates the bandwidth used when the desktop responds to print jobs issued by this user. 

Kbps

Speed screen data channel bandwidth input:

Indicates the bandwidth used from this user to the server 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.

These measures will be reported only if the collect extended metrics flag is set to ‘Yes’.

Speed screen data channel bandwidth output:

Indicates the bandwidth used from server to this user for data channel traffic.

Kbps

HDX media stream for flash data bandwidth input:

Indicates the bandwidth used from this user to server 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.

 

 

HDX media stream for flash data bandwidth output:

Indicates the bandwidth used from the server to this user for flash data traffic

Kbps

HDX media stream for flash v2 data bandwidth input:

Indicates the bandwidth used from this user to server 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.

 

 

HDX media stream for flash v2 data bandwidth output:

Indicates the bandwidth used from the server to this user for flash v2 data traffic

Kbps

Speed screen multimedia acceleration bandwidth input

Indicates the bandwidth used from this user to the server for multimedia traffic.

Kbps

Comparing the values of these measures across users will reveal which user has been transmitting/receiving bandwidth-intensive multimedia files.

This measure will be reported only if the collect extended metrics flag is set to ‘Yes’.

Speed screen multimedia acceleration bandwidth output

Indicates the bandwidth used from the server to this user for multimedia traffic.

Kbps

PN bandwidth input:

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’.

PN bandwidth output:

Indicates the bandwidth, used from the virtual desktop to this user by Program Neighborhood to obtain application set details.

Kbps

CPU time used by user’s sessions:

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 of 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.

Input bandwidth usage:

Indicates the percentage HDX bandwidth consumed by client to server traffic of this user.

Percent

Compare the value of these measures across users to know which user is consuming the maximum HDX bandwidth.

Output 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.

ThinWire bandwidth input:

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. 

This measure will be reported only if the collect extended metrics flag is set to ‘Yes’.

Thinwire bandwith output:

Indicates the bandwidth used from server to client for ThinWire traffic.

Kbps

Seamless bandwidth input:

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.   

This measure will be reported only if the collect extended metrics flag is set to ‘Yes’.

Seamless bandwidth output:

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.

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.

Total time in session:

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.

Active time in last measure period:

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.

Time since last activity:

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 time in session:

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 time in session 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 time in session measure for a user, it means that the user has been active for most part of the session.

Working set memory for user's processes:

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.

Virtual memory of user's processes

Indicates the amount of virtual memory used by the user's sessions.

MB

Compare the value of this measure across users to know which user is consuming the maximum virtual memory.

Processes running in the user's session:

Indicates the count of processes running in this user's session.

Number

 

Client network latency

Indicates the latency experienced by this user when transmitting/receiving data over the ICA channel.

Secs

This measure represents the network latency detected between the ICA client and the Citrix XenApp server being monitored.

If both the Screen refresh latency and Client network latency measures report high values, it implies that network slowness is contributing to user-perceived Citrix slowness (i.e., the problem is not due to the Citrix servers, but probably due to the network connection that the user is connecting from - e.g., a wireless WAN).

If Screen refresh latency is high and Client network latency is low, this implies that there is a bottleneck in the Citrix stack that is causing user experience to be poor (e.g., overloaded server or virtual platform, slowness in storage, etc.). Slowness can also occur because of client-side processing delays on the receiver end.

Frame rate:

Indicates the rate at which frames are processed during this user session.

Frames/Sec

FPS is how fast your graphics card can output individual frames each second. It is the most time-tested and ideal measure of performance of a GPU. Higher the value of this measure, healthier is the GPU.

Framehawk frame rate:

Indicates the rate at which frames are processed by the Framehawk virtual channel, if it is enabled for this user session.

Frames/Sec

The Framehawk virtual channel optimizes the delivery of virtual desktops and applications to users on broadband wireless connections, when high packet loss or congestion occurs.

A high value is desired for this measure, as it indicates faster delivery of applications to users, which in turn makes for a better user experience.  

You can compare the value of this measure with that of the Frame rate measure of a user to ascertain whether/not the Framehawk virtual channel has indeed enhanced that user’s experience with applications deployed on XenApp. If this comparison reveals that the value of this measure is higher than that of the Frame rate measure, it is a clear indicator of the effectiveness of the Framehawk virtual channel.

Note:

This measure will report the value 0 if Framehawk is not enabled for a user or if the device from which the user is accessing the application does not support Framehawk.

Framehawk network bandwidth:

Indicates the bandwidth consumption of this user session when the Framehawk virtual delivery channel is used.

KB

This is a good measure of the effectiveness of Framehawk in optimizing the bandwidth usage over the virtual delivery channel. A low value is desired for this measure.

Note:

This measure will report the value 0 if Framehawk is not enabled for a user or if the device from which the user is accessing the application does not support Framehawk.

Framehawk latency:

Indicates the latency experienced by this user session when the Framehawk virtual delivery channel is used.

Secs

To judge the effectiveness of Framehawk, compare the value of this measure with that of the ICA network latency measure for a Framehawk-enabled user. If the comparison reveals a lower value for this measure, it implies that Framehawk has succeeded in minimizing the latencies over the delivery channel.

Note:

This measure will report the value 0 if Framehawk is not enabled for a user or if the device from which the user is accessing the application does not support Framehawk.

Framehawk network loss:

Indicates the percentage of packet loss experienced by this user session when the Framehawk virtual delivery channel is used.

Percent

If the value of this measure is very low, it indicates that Framehawk has been very effective in minimizing the loss ofpackets that typically occur when data is transmitted or received over a channel.

Note:

This measure will report the value 0 if Framehawk is not enabled for a user or if the device from which the user is accessing the application does not support Framehawk.

 

Note:

When a Citrix user being monitored by the eG agent logs out of the Citrix server, then the name of the user will not be displayed as a descriptor of the this test in the eG monitor interface.

The detailed diagnosis of the User sessions measure (and the CPU usage of user’s processes and Memory usage of user’s processes measures), if enabled, provides the list of processes executed by a user on the Citrix server, and the CPU and memory utilization of such processes (see Figure 1). This information enables the Citrix administrator to identify the processes that are utilizing resources excessively and those that may be leaking memory. In the event of a server overload/memory leak, the Citrix administrator might decide to terminate these processes (see Figure 1). In addition, the detailed diagnosis reveals the location from which each application instance runs (i.e., the IMAGE PATH). If multiple versions of an application are published in different locations on the XenApp server and a user runs each of these versions, then the IMAGE PATH will indicate the exact application version each process instance corresponds to – resource-hungry versions can thus be identifed. Where one/more instances of the Internet Explorer browser are running, the detailed diagnosis additionally displays the website URL accessed using each IE instance, the domain of every URL, and the website title. In the event of excessive resource usage by an IE instance, this information will shed light on the resource-intensive web site that was being accessed.

Note:

  • The eG agent will perform browser activity monitoring only if the enable browser monitoring flag is set to Yes.
  • The eG agent will monitor browser activity only of the browser being accessed is Internet Explorer.

Figure 1 : The detailed diagnosis of the User sessions measure

The detailed diagnosis of the CPU time used by user’s sessions measure, if enabled, provides the list of processes executed by a user on the Citrix server, and the percentage of time for which each process was hogging the CPU. This percentage denotes the total percentage of time the process was using the CPU resources across all the processors that are supported by the XenApp server. This leads you to the exact process that is draining the CPU resources of the server. In addition, the detailed diagnosis reveals the location from which each application instance runs (i.e., the IMAGE PATH). If multiple versions of an application are published in different locations on the XenApp server and a user runs each of these versions, then the IMAGE PATH will indicate the exact application version each process instance corresponds to – resource-hungry versions can thus be identifed. Where one/more instances of the Internet Explorer browser are running, the detailed diagnosis additionally displays the website URLs accessed using each IE instance, the domain of every URL, and the website title. In the event of excessive resource usage by an IE instance, this information will shed light on the resource-intensive web site that was being accessed.

Figure 2 : The detailed diagnosis of the CPU time used by user’s sessions measure

Note:

  • The eG agent will perform browser activity monitoring only if the enable browser monitoring flag is set to Yes.
  • The eG agent will monitor browser activity only of the browser being accessed is Internet Explorer.