eG Monitoring
 

Measures reported by AppVAppsTest

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.

The measures made by this test are as follows:

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 applicaition 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 1
False 0

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.

Pct_loaded 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
True 1
False 0

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.

Is_usr_pending 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
Yes 1
No 0

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.

Is_global_pending 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 1
No 0

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.

Num_procs_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_util 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_util 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.
IO_data_oper_rate Indicates the rate at which this application process is issuing read and write data to file, network and device I/O operations. Operations/Sec  
IO_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.
IO_read_data_rate Indicates the rate at which the process is reading data from file, network and device I/O operations. Kbytes/Sec  
IO_write_data_rate Indicates the rate at which the process is writing data to file, network and device I/O operations. Kbytes/Sec  
No_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  
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.