Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloudor on-prem performance issues
Large enterprises often have load balanced groups of servers providing web, middleware, and database functionality. The servers in the group often perform the same functions and have the same set of dependencies on other infrastructure components. For a service with tens of servers in a group, the service topology representation can quickly get very cumbersome. To handle such environments, eG Enterprise allows administrators to define server groups that represent a collection of similar servers. By including a server group in a service topology representation, administrators can indicate that all the servers in the group have the same set of dependencies on other parts of the infrastructure. Topology representation using server groups are compact and concise to represent, and simple to understand.
To create a group, do the following:
The component groups page that appears next will display all the existing groups. If no groups pre-exist, then a message indicated by Figure 1 will appear.
Figure 2 will then appear. Here, specify the name of the group that is to be created in the Group name text box.
The Component type list will automatically be populated with all the component types that are associated with the chosen zone. Pick the component type of your choice from this list. The Available Hosts list will then be populated with the components of the chosen component type (see Figure 3). Select the hosts that you wish to add to the new group and click the < button. This will transfer your selection to the Associated Hosts list.
You will then return to Figure 4, which will list the newly created group. To modify the group, click on the icon against the group name. To delete a group, click the icon against the group. To mark all the displayed groups for deletion, select the check box against the Group Name label and click the icon.
When monitoring Citrix infrastructures, administrators often prefer to manage delivery groups on a Citrix Delivery Controller as Component Groups in eG. If an eG agent is installed on a Citrix Delivery Controller, then this agent can auto-discover all the delivery groups managed by the controller and the XenApp servers in each group. The eG manager uses the details so discovered to accurately identify the delivery group to which a managed XenApp server belongs. With this knowledge, the eG manager then automatically creates a component group in eG, adds the managed XenApp server to it, and also assigns the delivery group’s name (by default) to that component group. If later, XenApp servers are added/removed from a delivery group, eG Enterprise auto-detects this change and updates the corresponding component group configuration accordingly. This eliminates the need for any manual intervention in component group maintenance. To enable this capability, do the following:
By default, the component groups that eG auto-creates will be named after the delivery groups they represent. If you want the auto-created component group names to be prefixed by any string, then specify that string against the PrefixForAutoCreatedGroupNames flag.
If a delivery group is removed, then eG Enterprise will automatically remove the corresponding component group, only if that component group is not part of ay segment/service configuration. Likewise, if a delivery group is removed, then eG Enterprise will NOT remove those Citrix XenApp servers in the group that are included in a segment/service configuration as ‘independent servers’.