eG Monitoring
 

Measures reported by CtxCdAppGroupTest

Application Groups let you manage collections of applications. You can create Application Groups for applications shared across different Delivery Groups or used by a subset of users within Delivery Groups. Application Groups are optional; they offer an alternative to adding the same applications to multiple Delivery Groups. Delivery Groups can be associated with more than one Application Group, and an Application Group can be associated with more than one Delivery Group.

Using Application Groups, you can provide application management and resource control advantages over using more Delivery Groups:

  • The logical grouping of applications and their settings lets you manage those applications as a single unit. For example, you don’t have to add (publish) the same application to individual Delivery Groups one at a time.

  • Session sharing between Application Groups can conserve resource consumption. In other cases, disabling session sharing between Application Groups may be beneficial.

  • You can use the tag restriction feature to publish applications from an Application Group, considering only a subset of the machines in selected Delivery Groups. With tag restrictions, you can use your existing machines for more than one publishing task, saving the costs associated with deploying and managing additional machines. A tag restriction can be thought of as subdividing (or partitioning) the machines in a Delivery Group. Using an Application Group or desktops with a tag restriction can be helpful when isolating and troubleshooting a subset of machines in a Delivery Group.

Whenever users to a virtual desktop complain that they are unable to access an application, administrators should be able to quickly figure out whether/not that application is part of an application group. If it is, then the administrator should also be able to rapidly isolate the reason for the inaccessibility – is it because the application group is disabled? is it because the session-sharing is not enabled for applications in that application group? is it because the user is not allowed access to the application group? or is it because a tag restriction restricts user access to the application in question? The Application Groups test enables users to perform these checks.

This test auto-discovers the application groups in the delivery controller, and points administrators to the application groups that are currently enabled and those application groups that shared sessions with other application groups. In addition, this test reports the total number of applications in each application group and the number of machines (across all desktop groups) on which the application groups are published. In the process, this test also reveals the count of machines that are tagged with the tag given by the RestrictToTag property. Knowing the machines with tag restrictions, administrators can plan on using the existing machines for more than one publishing task, and thus saving the costs associated with deploying and managing additional machines.

Outputs of the test : One set of results for each application group that is to be monitored.

Descriptor of the test :Application Group

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Is_enabled Indicates whether/not this application group is enabled on this site.   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 above-mentioned Measure Values while indicating whether the application is enabled or not in this site. However, the graph of this measure will be represented using the corresponding numeric equivalents 0 and 1 only.

The detailed diagnosis of this measure if enabled, lists the tags and restricted tag applied to the application groups.
Is_session_share_enabled Indicates whether the applications in this application group can share sessions with applications in other application groups (or with applications that are not a member of an application group).   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 above-mentioned Measure Values while indicating whether/not the SessionSharingEnabled property is enabled for each application group. However, the graph of this measure will be represented using the corresponding numeric equivalents only.
Is_single_app_session Indicates whether/not SingleAppPerSession property is enabled.   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 above-mentioned Measure Values while indicating whether the SingleAppPerSession property is enabled or not. However, the graph of this measure will be represented using the corresponding numeric equivalents 0 and 1 only.

Note that, to enable the SingleAppPerSession property, you must set SessionSharingEnabled property to No. The two properties must not be enabled at the same time. The SessionSharingEnabled parameter refers to sharing sessions between Application Groups.
Is_user_filter_enabled Indicates whether the user filter is enabled in this application group.   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 above-mentioned Measure Values while indicating the priority level with which the application has to be processed. However, the graph of this measure will be represented using the corresponding numeric equivalents 0 and 1 only.

By enabling the filter, you can specify who can use the applications in the Application Group.
Total_apps Indicates the total number of applications in this application group. Number The detailed diagnosis of this measure lists the name of the application, the name of the application group to which the application belongs to, the delivery group to which the applications is associated with, the tag, the machine name and the user who is currently accessing the application.
Total_machines Indicates the total number of machines (across all desktop groups) on which this application group is published. Number  
Total_machines_with_tag Indicates the number of machines across all desktop groups on which this application group is published, and which are tagged. Number Tags are strings that identify items such as machines, applications, desktops, Delivery Groups, Application Groups, and policies. After creating a tag and adding it to an item, you can tailor certain operations to apply to only items that have a specified tag.
Restrict_tags Indicates the number of machines across all desktop groups on which the application group is published, and which are tagged with the tag given by the RestrictToTag property. Number Publish applications from an Application Group or specific desktops from a Delivery Group, considering only a subset of the machines in selected Delivery Groups. This is called a tag restriction.

With tag restrictions, you can use your existing machines for more than one publishing task, saving the costs associated with deploying and managing additional machines. A tag restriction can be thought of as subdividing (or partitioning) the machines in a Delivery Group.