Measures reported by CtxCdAppTest
With the Citrix Cloud, you provide users with access to information by publishing the following types of resources that can be virtualized on servers or desktops:
Applications installed on servers running Delivery Controller - 5. When users access them, the published applications appear to be running locally on client devices.
Streamed applications installed in application profiles and stored on a file server in your App Hub. Users access the profile and virtualize the applications on their client desktops.
Data files such as Web pages, documents, media files, spreadsheets, and URLs.
The server desktops, so users can access all of the resources available on the server.
All these types of resources are called Published applications.
Whenever users to a virtual desktop complain that they are unable to access one/more published applications, administrators should be able to quickly troubleshoot and figure out the reason for this - is it because the application is disabled on the site? Or is it because the application is not even visible to users?
In addition, administrators should also be able to periodically check how popular an application is (in terms of usage) and accordingly reset its CPU priority level, so that such applications always command more CPU resources and users have no problems accessing or continuously using such applications.
The CtxCdAppTest test enables users to perform these checks. This test points administrators to applications that are currently enabled on the site and those applications that are not visible to the users. In addition, this test reports the number of instances of an application that is currently running and the CPU priority level of each application, so that administrators can accurately isolate popular applications and their CPU priority level.
Outputs of the test : One set of results for each published application.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Is_enabled |
Indicates whether/not this application is enabled on the controller. |
|
The values that this measure reports and their corresponding numeric values are:
| Measure Value |
Numeric Value |
| Yes |
1 |
| No |
0 |
Note:
By default, this measure reports the values Yes or No while indicating whether the application is enabled or not. However, the graph of this measure will represent the same using the corresponding numeric equivalents of 0 and 1 only.
The detailed diagnosis of this measure if enabled, lists the name and type of the application, the location of the program file and the working directory. |
| Is_visible |
Indicates whether/not this application is visible to the users. |
|
The values that this measure reports and their corresponding numeric values are:
| Measure Value |
Numeric Value |
| Yes |
1 |
| No |
0 |
Note:
By default, this measure reports the values Yes or No while indicating whether the application is visible to users. However, the graph of this measure will represent the same using the corresponding numeric equivalents of 0 and 1 only. |
| No_of_instances |
Indicates the number of instances of this application that are currently running. |
Number |
Comparing the value of this measure across all the applications will help you to identify the application that is most often used by the users.
The detailed diagnosis of this measure if enabled, lists the name of the application, the application type, the name of the catalog and delivery group to which the machine belongs, the zone to which the delivery group belongs, the machine ID, the user accessing the application, the client name and IP address, the protocol used for establishing the session, the start time of the session, the number of sessions - if the session is a Single session or a Multiple session etc. |
| Cpu_priority |
Indicates the priority level that is set for the resource usage of this application. |
|
The values that this measure can report and their corresponding numeric values are:
| Measure Value |
Numeric Value |
| Low |
0 |
| Below Normal |
1 |
| Normal |
2 |
| Above Normal |
3 |
| High |
4 |
Note:
By default, this measure reports the above mentioned values while indicating the priority level with which the application has to be processed. However, the graph of this measure will represent the same using the corresponding numeric equivalents only. |
|