App-V Applications Test

This test reports statistics pertaining to the different applications executing on an App-V client and their usage. In addition, this test also reports the statistics pertaining to the processes running on the APP-V client.

Note:

This test will report metrics only when the App-V Client is installed on the Citrix XenApp Server.

Target of the test :An App-V Client on the target Citrix XenAPP Server

Agent deploying the test :An internal agent

Outputs of the test :One set of results for each application of the target App-V Client that is to be monitored

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 – The port at which the specified HOST listens. By default, this is NULL.
  4. REPORT BY DOMAIN NAME – By default, this flag is set to No. This means that, by default, the test will report metrics for each username only. You can set this flag to Yes, to ensure that the test reports metrics for each domainname\username.
  5. EXTENDED STATISTICS – By default, this test provides you with detailed measures on the resource utilization of each application. If you wish to obtain only the CPU and memory related measures, then set the EXTENDED STATISTICS flag to No.
  6. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eG Enterprise suite 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 enabled/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

Total size:

Indicates the total size of this virtual application package.

MB

The detailed diagnosis of this measure lists the Version of the application, Application ID, Version ID of the application and the application path.

Is loading?:

Indicates whether this application is currently loading or not on the App-V client.

 

This measure reports a value True if the application is currently being loaded and a value False if otherwise.

These measure values and their corresponding numeric values are listed in the table below:

Measure Value Numeric Value

True

0

False

1

Note:

By default, this measure reports the values Yes or No to indicate whether this application is currently being loaded on the client or not. The graph of this measure however is represented using the numeric equivalents - 0 or 1.

Loaded percentage:

Indicates the percentage of this application that is currently being loaded on the App-V client.

Percent

 

In use?:

Indicates whether this application is currently in use or not.

 

This measure reports a value True if the application is currently in use and a value False if otherwise.

These measure values and their corresponding numeric values are listed in the table below:

Measure Value Numeric Value

True

0

False

1

Note:

By default, this measure reports the values Yes or No to indicate whether this application is currently in use. The graph of this measure however is represented using the numeric equivalents - 0 or 1.

Any user based pending tasks available?

Indicates whether any tasks are pending for the user using this application.

 

This measure reports a value Yes if any tasks are pending for the user using the application and a value No if otherwise.

These measure values and their corresponding numeric values are listed in the table below:

Measure Value Numeric Value

True

0

False

1

Note:

By default, this measure reports the values Yes or No to indicate whether any tasks are currently pending for the user using this application. The graph of this measure however is represented using the numeric equivalents - 0 or 1.

Any global based pending tasks available:

Indicates whether any global tasks are pending for this application.

 

This measure reports a value Yes if any tasks are pending for the user using the application and a value No if otherwise.

These measure values and their corresponding numeric values are listed in the table below:

Measure Value Numeric Value

Yes

0

No

1

Note:

By default, this measure reports the values Yes or No to indicate whether any tasks are currently pending for the user using this application. The graph of this measure however is represented using the numeric equivalents - 0 or 1.

Processes running:

Indicates the number of instances of this application currently executing.

Number

This value indicates if too many or too few instances corresponding to an application are executing on the host. The detailed diagnosis of this measure, if enabled, displays the complete list of processes executing, the users executing them, and their individual resource utilization.

CPU utilization:

Indicates the percentage of CPU used by this application.

Percent

A very high value could indicate that the specified application is consuming excessive CPU resources.

Memory utilization:

This value represents the ratio of the resident set size of the memory utilized by the application to the physical memory of the host system, expressed as a percentage.

Percent

A sudden increase in memory utilization for an application may be indicative of memory leaks in the application.

Handle count:

Indicates the number of handles opened by this application.

Number

An increasing trend in this measure is indicative of a memory leak in the process.

I/O data rate:

Indicates the rate at which processes are reading and writing bytes in I/O operations.

Kbytes/Sec

This value counts all I/O activity generated by each process and includes file, network and device I/Os.

I/O data operations:

Indicates the rate at which this application process is issuing read and write data to file, network and device I/O operations.

Operations/Sec

 

I/O read data rate:

Indicates the rate at which the process is reading data from file, network and device I/O operations.

Kbytes/Sec

 

I/O write data rate:

Indicates the rate at which the process is writing data to file, network and device I/O operations.

Kbytes/Sec

 

Number of threads:

Indicates the number of threads that are used by this application.

Number

 

Page fault rate:

Indicates the total rate at which page faults are occurring for the threads of all matching application processes.

Faults/Sec

A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This may not cause the page to be fetched from disk if it is on the standby list and hence already in main memory, or if it is in use by another process with whom the page is shared.

Virtual memory used:

Indicates the amount of virtual memory that is being used by the application.

MB

 

Memory working set:

Indicates the current size of the working set of a process.

MB

The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer 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 a process pattern matches multiple processes, the memory working set reported is the sum of the working sets for the processes that match the specified pattern. Detailed diagnosis for this test provides details of the individual processes and their individual working sets.

Comparing the working set across processes indicates which process(es) are taking up excessive memory. By tracking the working set of a process over time, you can determine if the application has a memory leak or not.