In PerformanceGuard there are several ways in which you can group computers that have PerformanceGuard agents installed. When computers are grouped, it becomes easy to compare performance data between locations or other dimensions, for example departments or users of particular applications.
One way of grouping happens automatically (but you can configure how it should happen). The automatic grouping means that you don't need to create any groups yourself in order for PerformanceGuard to work—you can create your own groups if and when you need them.
The other ways to group computers are manual. This lets you tailor your computer group structures to match the exact needs of your organization.
Let's take a look at the different ways to group computers in PerformanceGuard:
PerformanceGuard automatically groups computers that belong to the same IP subnet into the same group. PerformanceGuard does this based on each computer's IP address and subnet mask.
In PerformanceGuard such a group is called a network group, because only computers that belong on a certain part of a network can be members of this group. Only PerformanceGuard can place computers in network groups.
Network groups are dynamic: If a computer is moved to another subnet (that is the computer's IP address information changes), PerformanceGuard will automatically move the computer to the network group that matches. If there isn't already a network group that matches, PerformanceGuard will automatically create one.
Explain the _ctx concept that replaces the old CitrixServer grouping |
|
|
|
To sum up the characteristics of network groups:
You can only do this if you're a PerformanceGuard administrator. |
Because PerformanceGuard automatically groups computers based on their network details, you don't need to set up groups yourself. However, it can sometimes be a good idea to create your own groups as a supplement to the automatically created network-based groups.
Example: Your organization consists of several regional offices. At each of the offices there are a few users who use a special finance application on their computers. You would like to be able to view performance data for users of this finance application. You create a group that contains the computers of those users. Now you can view performance data for that group, even though the computers are not on the same network. |
You are able to do this because computers can be members of more than one group in PerformanceGuard. In other words, you can group your organization's computers by as many dimensions as you like. For example, you can group computers by user profiles. This can be useful because secretaries, accountants, salespeople and managing directors often use their computers differently. They may also have very different performance requirements, and you may want to measure their quality of experience separately.
In PerformanceGuard such a group that you create yourself is called a user-defined group.
User-defined groups are static: Computers will remain in user-defined groups until you remove them, even if computers are moved to another network. User-defined groups are completely independent of the automatically created network groups. This also means that—unlike the network groups—user-defined groups are not automatically removed if they become empty.
How do user-defined groups work in a Citrix environment? When you create a user-defined group, PerformanceGuard asks you whether you want to create a regular user-defined group or a special user-defined group for Citrix servers (in Citrix environments, PerformanceGuard agents are installed on the Citrix servers rather than on individual computers). The difference is that only the special groups for Citrix servers are visible in the Citrix section of the PerformanceGuard web interface (ANALYZE > Citrix), whereas regular user-defined groups won't appear in the Citrix section.
Create Your Own Groups of Groups: Super Groups and Locations
You have a very high degree of flexibility, because:
Example: Click thumbnail to view image in full size.
A location must relate to at least one network group (i.e. it must contain a network group, or it must contain other locations or super groups that ultimately contain at least one network group). |
|
|
Search this documentation On this page In this section |