Groups determine the data that you see in dashboards when you log in. The group that is applied as a filter to the current dashboard is the group context for that dashboard. When you log in to CA npc, the pages reflect the context of your default permission group. You can change the default group for your user account to view data from another group in the dashboards.
Groups determine the data that you see in dashboards when you log in. The group that is applied as a filter to the current dashboard is the group context for that dashboard. When you log in to CA
Performance Center
, the pages reflect the context of your default permission group. You can change the default group for your user account to view data from another group in the dashboards.
Groups are organized into a hierarchical tree structure. The Groups tree helps you define relationships, policies, and dependencies among services, devices, applications, locations, and users within your organization. Organize your group structure according to business and reporting needs. To create a regional structure that represents regions, countries, and locations, use site groups. Use custom groups for other types of organizations, such as customers, services, or technologies.
Threshold profiles apply threshold rules to all items in a group. The group hierarchy requirements for thresholding are probably different from the requirements for reporting. Create separate groups that address both sets of requirements. Consider the different layers of the network and how to create thresholds for components in those layers. For example, you might threshold on CPU, memory, and interface metrics on the core network differently to the distribution layer. Create multiple groups to apply threshold rules appropriately.
Tenants include special types of system groups to maintain separation among customer deployments. Tenants can also contain entire custom grouping structures.
The lock icon that appears on a group icon, such as System Groups, indicates that a group cannot be edited.
The following video introduces the concept of groups in
CA Performance Management

System Groups
System Groups are read-only groups that are automatically created based on information from data sources. System groups can be viewed, applied as permission groups to user accounts, or copied to custom or site groups.
Inventory Group
The Inventory group includes all managed items that are discovered by all registered data sources. This group also organizes data sources, IP domains, and managed items in subgroups. The Inventory group contains its own system subgroups to organize managed items by their type.
[email protected] groups, such as [email protected], are not synced to data sources. These groups cannot be used for reporting, or as default user groups. Using these groups causes synchronization errors.
The following system groups appear under the Inventory node:
  • All Items
    Includes subgroups of managed items, which are categorized by type.
    • All Pingable Devices
      Includes all discovered devices that cannot be contacted using SNMP.
    • ESX Hosts
      Includes all VMware servers that host virtual machines.
    • Interfaces
      Includes router and switch interfaces from all data sources.
    • Routers
      Includes all routers from all data sources.
    • Servers
      Includes all servers from all data sources.
    • CA Application Delivery Analysis Networks
      Includes all networks that CA Application Delivery Analysis (CA ADA) has observed. A CA ADA network consists of an IP address and mask.
    • Switches
      Includes switches from all data sources.
    • Virtual Machines
      Includes all virtual machines running on all ESX servers.
  • Data Sources
    Includes all registered data sources. Each data source has a dedicated group under this node. Some data sources have their own system subgroups, which appear when you expand the data source group.
    Some data sources, such as Data Aggregator and Event Manager, do not have groups. The groups are not designed as reporting groups and might not provide data when selected as the context.
  • IP Domains
    Includes all custom IP domains that are created by the administrator. Also includes the Default Domain, which contains all items that are not explicitly assigned to a custom domain. For more information, see IP Domains.
  • VNA Domains
    These groups contain hierarchically organized items from
    CA Virtual Network Assurance
    . The structure groups the items into logical reporting groups. Use these groups for reporting. The highest level groups under this node are user configurable in
    CA Virtual Network Assurance
The collections group represents the collections of devices. Collections are groupings of devices that are monitored using the rules that are specified in monitoring profiles. The factory collections are not visible in the Groups tree. Collections include only devices.
This group lets you create custom collections. Any subgroup that you add to the Collections group is synchronized to the Data Aggregator as a collection.
Custom Groups
Custom groups create hierarchical levels and organize items into logical relationships within the Groups tree. Custom groups at the top level of the Groups tree represent geographical, topological, or functional divisions within your organization. Lower-level custom groups, or subgroups, typically represent one of the following options:
  • Applications
  • Devices
  • Job functions of IT staff
  • Services
Only users that have the "Administer Groups Owned by You" role right can create and edit custom groups, which filter the data in dashboards and views. The group context for a dashboard or view determines the data that is presented.
Custom groups are used to monitor and manage your system. Creating custom groups lets you organize data and assign operator permissions to access data.
You can use group rules to add items to groups automatically as they are discovered. Setting up rules makes it easier to populate and maintain groups. You can also populate custom groups by manually adding specific items, such as routers or interfaces that are logically or geographically related.
Site Groups
Site groups are special custom groups that are based on sites, such as branch offices, or on physical locations, such as regions or cities. Site groups let you create navigation functions within dashboards to present views across all sites. They include a Time Zone and a Business Hours parameter to let you see prioritized data from business-critical times of day.
Site groups also provide a granular context to apply to dashboards. For example, after you create a site group for each of your sites, a single dashboard can individually report on each site. Create a site group for each data center within your enterprise, and for other major infrastructure locations.
Groups for Multi-Tenant Deployments
When the administrator for the Default Tenant creates at least one tenant, features to support multi-tenancy are enabled. Multi-tenant deployments consist of multiple discrete enterprises with IP addresses that might overlap. More groups appear in the Groups tree to let the administrator organize tenant inventories and allocate permissions:
  • Defined Tenants
    The Defined Tenants group includes all tenants. Tenants are used with IP domains to monitor separate customer environments with a single CA
    Performance Center
    instance. Each tenant can contain multiple subgroups of items that are not shared among tenants.
    Tenant administrators can create custom groups within their tenant. For the global administrator, tenant groups appear under the Tenant node in the Groups tree.
  • Service Provider Global Groups
    Service Provider Global Groups contain groups of items that help the global administrator manage tenant environments. These groups let the administrator visualize and organize shared items, which are not explicitly associated with a tenant IP domain. The groups that allocate access to data from shared items appear under each tenant.
    When you expand the top-level Inventory group, the following group appears in a multi-tenant deployment:
  • Domains
    Includes all custom IP domains that are used to associate managed items with tenants. Also includes the Default Domain, which contains all items that are not explicitly assigned to a custom domain. For more information, see IP Domains.
In a multi-tenant deployment, each tenant has its own groups. Tenant users cannot see items outside of the tenant group unless the global administrator grants access with Service Provider groups.
  • Groups (Tenant)
    Lets the global administrator or tenant administrator create custom groups. Select this node to enable the Add Group button.
  • Inventory (Tenant)
    Includes all managed items that are associated with the tenant IP domains. Items from all registered data sources might appear in this group.
Each tenant also has the following system subgroups in its Inventory group:
  • IP Domains
    The IP Domains subgroup represents the IP domains that are associated with this tenant. Any managed items that have been discovered are associated with this tenant through its IP domains. To see the managed items of the tenant, click a tenant IP domain in the Groups tree.
  • Service Provider Defined Groups
    The Service Provider Defined Groups include groups that the global administrator has populated with shared items that this tenant can access. Use these groups to grant access to data from shared devices to selected tenant user accounts. 
    For example, a router that the service provider owns handles traffic from multiple tenant domains. Using Service Provider Defined groups, the global administrator can allocate tenant access to data from that router. The tenant can then independently monitor and verify system performance.
  • Service Provider Items
    Items that are not explicitly associated with a tenant IP domain are automatically placed in the Service Provider Items group. The global administrator can place these items into Service Provider Defined Groups to allocate tenant access to data from shared items.