Create and Manage Groups in USM

Using groups, you can:
uim851
usm_groups
This articles describes how to configure groups in USM. Groups are lists of computer systems or interfaces.
Using groups, you can:
  • Organize your infrastructure by location, technology, or even a service. For example, you could create a container group named e-Commerce, a business service. The e-Commerce group could contain three groups named Web Servers, Application Servers, and Database Servers. These could be either dynamic or static groups and would contain servers to support each aspect of the e-Commerce service.
  • View out of box reports that generate information about all of the members in each group.
  • Assign report templates to each group. 
  • Set maintenance windows for groups. Systems in maintenance only generate informational alarms. 
There are four types of groups that you can use:
  • Container
    - A parent to other groups.
  • Dynamic
    - Contains the computer systems or interfaces that meet a specified set of criteria. Dynamic groups can be created manually, or UMP can automatically create groups based on OS Type, OS Name, Origin, User Tag 1, or User Tag 2. The membership of dynamic groups is updated automatically on a configurable interval.
  • Static
    - Contains a specified list of computer systems or interfaces. Once you specify the list of systems or interfaces that are members of the group, the membership does not change unless you manually add or remove systems.
  • Interface
    - Interface groups are unique groups for networking devices. You can create and filter interface devices as you would for other computer systems. However, interface devices have a unique report located on the
    Interfaces
    tab.
Contents:
Create a Group
You must have USM Group Modifications permission to create, edit, and delete groups in USM.
Follow these steps:
  1. In a badge or tree view, click on a container group and select 
    Add Group
    from the
    Actions
    menu or hover to the right of an existing group and click on the
    +
    symbol.
    You can only add a new group under an existing container (Parent) group.
  2. In the
    Properties
    tab, edit the settings as needed:
    • Group Type
      - Choose
      Container
      ,
      Dynamic
      , or
      Static
      .
    • Member Type
      - Choose
      System
      or
      Interface
    • Name
      - Enter a name for the group.
    • Description
      - Enter a description of the group.
    • Account
      - Choose
      No Account
      if you do not want account contact users to see the group. Or, select an account so that only account contact users assigned to that account or bus users can see the group (account contact users from other accounts cannot see the group).
    • Filters
      - Define a filter to populate the group.
      Click
      Apply Filters
      to list discovered systems for a new group. 
      All listed systems are included when you create a Dynamic group. You must select at least one listed system to create a Static group by selecting it in the
      Included
      column. You can modify existing groups by changing the filters for a Dynamic group or selecting and deselecting systems from the filtered list for a Static group.
      Once you create a group, you cannot change the group type. To change the group type, you have to delete the group and create a new group with another type.
  3. In the
    Report Templates
    tab, edit the settings as needed:
    • Add Template
      - Choose a template from the menus in the Report Templates window.
    • Delete Template
      - Select a template and delete it from the list.
    • Default
      - Set a template in the list as the default for group reports.
      No report templates are available for Container or Interface groups.
  4. Click
    OK
    at the bottom of the window.
Create a Group to Display Auto-Scaling Metrics for AWS
Amazon auto-scaling groups (ASGs) are dynamic groups in which resources are allocated according to network demand, optimizing resource usage and operating costs. Amazon Web Services (AWS) Elastic Compute Cloud (EC2) instances move in and out of an ASG based on rules for on demand constraints (CPU, memory, etc.). The aws (Amazon Web Services Monitoring) probe generates QoS data and alarms that are based on the performance of various AWS service instances.
ASGs are configured in the AWS Management Console. The aws probe is then deployed and configured for instances in those groups, and USM groups are created to display the ASG groups, their devices, and their metrics. You must create an auto-scaling group in USM for each group defined in the AWS Management Console. You must enter the attribute
AWSAutoScalingGroup
for the Advanced filter attribute manually for each ASG.
Follow these steps:
  1. Install the prerequisite parameters in USM to display ASG metrics. These parameters are listed in USM Prerequisites.
  2. Create ASGs in the AWS Management Console. For more information, see the AWS documentation at http://aws.amazon.com/autoscaling/.
  3. Deploy the aws probe, version 3.5 or later, and create a resource for your AWS account. The aws probe discovers the ASG groups and publishes this information to the DB. For more information about configuring the probe, see the CA probe documentation.
  4. Create groups in USM for each ASG. Use the Advanced filter attribute
    AWSAutoScalingGroup
    and ASG names for the values.
Add a Filter
You can set various filter options to select the members for each group you create. Filters for both System and Interface type groups include:
  • Boolean operators
    and
    ,
    or
    , and
    not.
    Precedence among Boolean operators is NOT, then AND, and then OR. The order of multiple filter conditions does not affect the result.
  • A pulldown list of previously discovered properties. You can also enter an SQL query from the properties list.
    : To use the SQL query option, you must be a bus user with Portal Administrator permissions. Also, queries must include the column
    cs_id
    for devices and
    me_id
    for interfaces.
  • A condition list (
    is
    ,
    contains
    ,
    starts with
    , ...)
    The conditions list also contains the option
    undefined
    for properties without defined values. When the option
    undefined
    is selected, the values field is disabled.
  • A values field.
For static groups, create the filter and then select which of the listed systems to include in the group. For dynamic groups, create a filter to specify the systems to add to the group. The list of members in the dynamic group is automatically updated every 5 minutes.
Follow these steps:
  1. Click on the group type in the
    Group Type
    menu.
  2. Check to see that System is selected in the
    Member Type
    field.
  3. In the
    Filters
    section of the
    Properties
    tab, select items from the pull-down menus and enter text in the text field as appropriate.
    The filter condition
    undefined
    selects for attributes without defined values. This would be useful, for instance, if you wanted a group of all systems that didn’t have an operating system discovered. When the option
    undefined
    is selected, the values field is disabled.
    The filter conditions
    starts with
    ,
    contains
    ,
    and
    ends with
    allow you to simplify your filtering rules by use of wildcards:
    • %
      for one or more characters, and
    • _
      for one character
    Escape characters are recognized:
    • \%
      or
      [%]
      will look for a
      %
      symbol, and
    • \_
      or
      [_]
      will look for a
      _
      symbol
      The square brackets ([ and ]) escape characters do not work with the Oracle DB. You can only use the backslash (\) as the escape character if you are using the Oracle DB.
    The filter condition
    in
    allows you to list multiple attribute values in one filter rather than setting individual
    OR
    filters for each value. For example:
    MultipleFiltersWithValues.png
    can be represented with a single filter:
    SingleFilterWithMultipleValues.png
    You can copy a list of values from another source, paste the list into the values box, and apply the filter against all values. Each value must occur on a separate line and include no punctuation at the end.
  4. Click the
    Add Filter
    icon to add filter rows, the
    Delete Filter
    icon to delete filters that are not needed, and the
    Up
    and
    Down
    arrows to change the order of filters.
  5. When you have defined the rows for the filter, click the
    Apply Filters
    button to confirm the results in the
    Members
    table. Systems that have not yet been added to the group are shaded in gray.
    Not all systems that match the filter criteria can be displayed; up to 100 systems that match the filter are displayed. For dynamic groups, all systems that match the filter are included in the group, even if they are not displayed in the
    Members
    table when you click
    Apply Filters
    . To view all members in the group, save the group and click on the group in a badge or tree view. For static groups, existing group members are displayed in addition to the filter results. If more than 100 systems match the filter and you do not see the systems that you want to add to the group, you might need to refine the filter criteria so that the systems you want to add are displayed in the
    Members
    table.
  6. If the filter is for a static group, click the boxes in the
    Included
    column to select the systems to add to the group.
  7. Click
    OK
    .
The filter is saved and the systems added to the group are no longer shaded in gray in the
Members
table.
Add an Advanced Filter
If you have auto discovery enabled, you can filter on advanced attributes, such as PrimaryDnsName or Virtualization Environment, for system and interface groups. The filter field allows you to select from a list of discovered attributes or enter a known attribute that is not in the list.
Follow these steps:
  1. In the new group definition screen, pull down the
    Filters
    type menu.
  2. Click the
    Advanced
    option at the bottom of the menu.
  3. Click the attribute list icon ( USMGroupFiltersAdvancedEdit.png ) to bring up the list of attributes. If the needed attribute is not in the list, enter it.
    The pulldown list is populated automatically with attributes of discovered group members.
  4. Pull down the menu for the operator and select an operator.
  5. Enter a value in the values field.
  6. Click the
    Apply Filters
    button. 
  7. Click
    OK
    to save the group definition.
Filters for Amazon EC2 Instance Groups
You can control group members for any Amazon EC2 instance. For more information, see the AWS documentation at http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html. This functionality requires version 4.1 or later of the aws probe and version 8.401-SNAPSHOT or later of Discovery Server .
The following types of filters are available:
  • General filters:
    • OS Type
    • IP Address
    • Vendor
  • Advanced filters:
    • VirtualizationEnvironment
    • ComputerName
    • AWSInstanceState
    • AWSInstanceType
    • VMName
    • AWSMonitoringState
    • NumberOfInterfaceCards
    • OtherIPAddresses
    • AWSAvailabilityZone
    • PrimaryDNSName
    • OtherDNSName
  • AWS Management Console dynamic tags
    • Tags are defined in AWS Management Console, and appear as advanced filters with the format
      UserProp.
      <name>
      .
User Tags
You can filter on two user-defined criteria, called User Tags, in portlets that have filters. You can also automatically create groups according to User Tag.
User Tag 1
and
User Tag 2
are text fields that are configured in the controller robot for the hub. Once you have done so, you can filter for these values in the Unified Service Manager, Performance Reports Designer, and List Designer portlets.
For example, you could use
User Tag 1
for geographic location and
User Tag 2
for type of server. For some systems, you enter
Europe
for
User Tag 1
in the robot configuration, and for some systems you enter
Asia
. For
User Tag 2
, you enter either
production server
or
web server
.
You can then create reports for your regional systems by filtering on
User Tag 1
in the Performance Reports Designer (in the
Filters
tab) or List Designer (in the filter fields of the
New Group
pane). To do so, you would set the filter to
User Tag 1 is Europe
or
User Tag 1 is Asia
.
1938170.png
In the Unified Service Manager portlet, you can create separate groups for your production and web servers and apply different monitoring templates to them. To create the groups, in the
Filters
section of the Edit Group dialog you would set the filter to
User Tag 2 is production server
for one group, and
User Tag 2 is web server
for the other group.
2025615.PNG
User Tag 1
and
User Tag 2
can be used to filter for any system that has a robot running on it. You cannot use
User Tag 1
and
User Tag 2
to filter for network devices that do not have a robot.
Create Groups Automatically
USM can automatically create dynamic groups according to certain criteria.
In order to create groups automatically, you must not be an account contact user. For account contact users, the Configure Automatic Groups tab is not active.
Follow these steps:
  1. Click the
    Administration
    ( 1993051.PNG ) icon in Unified Service Manager.
  2. Click the
    Configure Automatic Groups
    tab.
  3. Select the type of automatic groups to create.
    Choosing more than one type of automatic group does not combine the types; each property you select creates groups for that property.
  4. If you want to create a group to be a parent of the automatic groups, enter a name in the
    Parent Group
    field.
    For example, if you are an MSP and create automatic groups by origin, you can name the parent group Customers. If you leave the
    Parent Group
    field blank, the automatic groups are created under the root node.
  5. Click
    OK
    .
The Servers Group
The
Servers
group is an automatic group that comes preconfigured with UMP. The
Servers
group creates sub-groups according to OS Type (Windows, Unix, and so on).
You cannot edit the properties of the
Servers
group or its sub-groups. However, you can assign monitoring templates and report templates. For the subgroups, you can also click the Apply Filters icon to view the results for the update of  the group .
Configure the Update Interval for Automatic Groups
You can change the update interval for automatic groups by configuring the nis_server probe.
Follow these steps:
  1. In Infrastructure Manager or Admin Console, select the system robot running UMP.
  2. Open the nis_server probe in Raw Configure.
  3. Navigate to the Setup section.
  4. Edit the value for the parameter group_maintenance_interval.
    Interval units are given in minutes.
The nis_server probe automatically restarts after the configuration change is made.
Set Maintenance Windows for Groups
The maintenance mode feature lets you temporarily suppress monitoring so that only informational alarms are generated for systems.
The maintenance mode feature in USM replaces the deprecated Maintenance Mode portlet.
You can schedule recurring maintenance to perform routine system updates. Or, you can place systems in a schedule that runs once only.
You can also create an ad hoc maintenance schedule if an unplanned outage occurs so that you can quickly respond to the outage.
To manage maintenance schedules, you must have the
Edit Maintenance Mode Schedules
permission set in the Access Control List (ACL). To manage the systems in maintenance schedules, you must have the
Edit Maintenance Mode Devices
permission set in the UIM ACL.
Create or Edit a Maintenance Schedule
A maintenance schedule must be created before you can add systems to the schedule.
Follow these steps:
  1. Select a group in the USM navigation tree, then select the
    Maintenance tab
    .
  2. Click the
    New Schedule
    button. Or, to edit an existing schedule, select the gear icon next to the schedule you want to edit.
    The
    Maintenance Schedule
    window opens.
  3. In the
    Maintenance Schedule
    window:
    1. Enter a name, or update the existing name. If desired, enter a description.
    2. Select an account for the maintenance schedule if desired.
    3. Make a selection under the
      Scheduling
      heading.
      The
      Schedule Recurrence
      options to the right update dynamically based on your selection.
    4. Select from the options under
      Schedule Recurrence
      and
      Maintenance Window
      as desired.
The new schedule is displayed, and you can add groups and systems.
Add Groups to a Maintenance Schedule
After a maintenance schedule is created, you can add groups or systems to the schedule.
Groups and systems can be added to multiple maintenance schedules.
Follow these steps:
  1. Browse to a group in the USM navigation tree, and select the
    Maintenance
    tab.
    You can expand groups to display individual systems, but the
    Maintenance
    tab is only displayed when a group is selected in the navigation tree.
  2. Hover over the handle icon (indicated by three horizontal lines) next to a group or system, and use the grabber icon to drag-and-drop systems to a maintenance schedule.
    You can also use the
    Search
    field to find systems that do not belong to a group. Drag systems from the
    Search Results
    node in the navigation tree.
    The maintenance schedule is updated and lists the system or group that you added. The wrench icons indicate that a group or system belongs to at least one maintenance schedule.
Configure Group Reports
If you select a group, the following reports are available:
  • Top N
  • Situations to Watch
  • Group Trend
You can also:
  • Assign more report templates to groups in USM. After a report template is assigned to a group, users can view the report for any system in the group. USM comes with a default report template. In addition, there are ready-made report templates with server usage and performance information.
  • Create reports in the Performance Reports Designer and assign them as report templates to groups in USM. You can designate which report template is the default report. The default report is launched when users click the
    Reports
    button. There must be one report template that is designated as the default, and the default template cannot be deleted.
  • View a dynamic report for a USM group. You can assign report templates to groups in USM. After a report template is assigned to a group, users can view the report for any system in the group.
Assign a Report Template to a Group
Administrators who have the USM Group Modification permission can assign report templates to groups in USM. Once you assign the report template to a group, users can view the report for any system in the group.
Follow these steps:
  1. In a badge or tree view, click on a group and click
    Edit Group
    in the
    Actions
    menu. Or, in the tree view mouse over the name of a group and click the Edit Group icon. The Edit Group <Group Name> dialog is displayed.
  2. Click the
    Report Templates
    tab.
  3. Click
    Add Template
    . The Report Templates dialog is displayed. If you are an account user, you see only the report templates that are not private to another account or to another user. Otherwise, you see all report templates that are not private to another user.
  4. Select the report template that you want to add, then click
    Add
    . The report template that you added is assigned to the selected group and all groups and systems under it in the tree.
  5. (Optional) To select a report template as the default report for the group, click the option button in the
    Default
    column for that template. The default template is the report that is launched when users click the
    Reports
    button in USM. There must be one report template that is designated as the default, and the default template cannot be deleted.
View Group Assignments
You can use the
Groups
tab of Unified Service Manager to view which groups a computer system is assigned to. This can help you determine whether any monitor collisions occur and how to set priority for your groups.
Follow these steps:
  1. In a badge or tree view, click on a computer system.
  2. Click the
    Groups
    tab in the right pane.
    The table displays the name of the group, the type of group (container, dynamic, or static), the priority set for the group, and the state set for the group (active or inactive).
Change a Group Parent
You can move container, system, and interface groups from one parent to another to reflect changes in organization. The following conditions apply:
  • Groups can only be moved from one container group to another.
  • Groups cannot be moved into an Automatic group, and an Automatic group cannot be moved into another parent.
  • Group location must honor tenancy: that is, a group can only be moved to a new parent with the same assigned account as its previous parent.
  • Group names must be unique under a single parent: that is, two groups with the same name cannot exist in the same parent.
Follow these steps:
  1. Hover over or select a group from the tree view in USM.
  2. Click on the
    Gear
    icon ( USMTreeGear.png ) to the right of the group name.
    An
    Edit
    window appears.
  3. Click on the
    Parent
    name in the
    Properties
    tab.
    A
    Select Group
    window appears.
  4. Select a group as the new parent.
    The names of groups that are not valid parents are greyed out. Tooltips display the reasons that they are not valid.
    To avoid duplicate group names under a parent, change the name of the group in the
    Edit
    window, click
    OK
    to save the change, and then repeat the steps to change the parent of the group.
  5. Click
    OK
    in the group selection window.
  6. Click
    OK
    in the
    Edit
    window.
Groups are displayed immediately under their new parents in USM.
Group names are honored in saved Analysis Reports that point to the group.
Delete a Group
You can delete a group if you no longer need it. For container groups, all subgroups must be deleted before you can delete the container group. For automatic groups, you must turn off the group in the Configure Automatic Groups tab in the Administration window in order to delete it.
Follow these steps:
  1. For automatic groups, click the
    Administration
    ( 1993051.PNG ) icon, deselect the group in the Configure Automatic Groups tab, and click
    Save
    .
  2. In a badge or tree view, click on the name of a group that does not have child groups.
  3. Choose
    Delete Group
    from the
    Actions
    menu
    OR
    In the tree view, mouse over the name of the group and click the
    Delete Group
    (trashcan) icon.
If you are running Application Discovery, you can delete an application group from the USM tree view without first deselecting it in the Administration window. When you delete the group in the tree view, it is automatically deselected in the Administration window.
If you are running Application Discovery and you delete the Systems group, you disable the Application Discovery feature. To restore the feature, you must deploy a v7.90 or later robot to all of the devices that you want to discover and monitor. After you deploy the robots, you must rerun discovery to restore the Systems group and the Application Discovery feature.
Restore a Group
You can restore a deleted automatic or preconfigured group by re-selecting the group in the
Administration
window.
Follow these steps:
  1. In USM, click on the
    Administration
    icon ( 1993051.PNG ).
  2. In the
    Configure Automatic Groups
    tab, click the empty box to the left of the group name to select it.
  3. Click the
    Save
    button.
Group profiles and filters are automatically run to retrieve device data.
Send Group Information to Digital Operation Intelligence (DOI)
You can publish group information such as group creation, update, or deletion from UIM to DOI (Digital Operational Intelligence). The axagateway probe creates different queues for alarms, groups and inventories. The probe then subscribes to these queues and posts data to DOI. For more information about configuring the axagateway probe to subscribe to group information, see the 
Enable Alarm, QoS and Inventory Subscription 
section in axagateway AC Configuration. In addition to configuring the axagateway probe, ensure that the following components are configured to publish the UIM group data to DOI:
  • WASP
    :
    Configure the wasp probe to allow publishing of group information. Set the value for 
    is_Group_Info_Publish 
    key
     
    as
     True
     to publish group updates such as group creation, update, and deletion to the 
    group_info
     queue.
    • The 
      group_info
       queue is created on the hub when you create, update, or delete a group after configuring the value for 
      is_Group_Info_Publish
       key as 
      True
      .
    • Configure the wasp probe on the computer where UMP is installed.
    To add the 
    is_Group_Info_Publish 
    key, follow these steps:
    1. Navigate to the 
      Raw Configure
       interface > 
      setup
       section.
    2. Add a new key
       is_Group_Info_Publish 
      and set the value as
       True
      .
        
      If you do not want to publish the group information, set the value as 
      False
      .
    3. Save the configuration and restart the wasp probe.
  • NISAPI
    :
    Any group changes such as group creation, update, or deletion done using API calls are published to the 
    group_info
     queue with the assumption that the key 
    is_Group_Info_Publish 
    in the wasp probe is set to 
    True
    .
    If the value for the key 
    is_Group_Info_Publish
     is set to False, group information is not published to the 
    group_info
     queue.
  • UIMAPI
    Any group changes such as group creation, update, or deletion done using API calls are published to the 
    group_info
     queue.
Enable and Configure a Health Index Score for a Group
For more information about how to enable and configure a Health Index score for a group, see the article
health_index
in the CA UIM Probes documentation.