Configure Universes

Universes let the administrator refine the number and types of components into easy to use authorization groups. This refined group is a universe. For security reasons, there is no default assignment to all users. To view
, each user must be allocated to a universe. If no universe is associated with the user ID, the user is warned. As an administrator, create universes for users. Use the default universe, named
All Components
, or create a custom universe.
The administrator performs the following tasks to configure universes:
  • Creates a universe to the needs of users or user groups.
  • Applies a filter to select component data from the data set.
  • (Optional) Creates numerous universes to create a series of manageable spaces. Users can easily switch between the spaces to make navigation of the environment easier.
  • (Optional) Ensures that specific user access is restricted as required by company security requirements.
Create a universe based on domains. Create a
Metric Sources
filter and use the same regular expression/s from your domain definition. Create a filter for the map components that is based on the
attribute, select the domain that you require and select
As an APM administrator, assign at least one universe to each user so they can access content.
A universe consists of:
  • A name - a unique identifier
  • A description - optional text to describe the universe
  • Filters:
    • Metric Source filter - applicable in a Metric view and in Metric charts in the Map view.
    • Map Components filter - applicable in all map-based views, namely Map view, Dashboard view, Experience view, and Agent view.
    • Management Module filter - applicable when viewing management module contents. For example, alerts in the Map or Dashboard. Also, setting definitions of calculators, metric sources, and alerts.
  • A list of users – users with access to this universe
Predefined Universes
Some universes are created by default:
  • The
    All components
    universe is created automatically and contains all components in the map, metric source, and management modules.
  • The
    universe includes all components in the environment. This universe built-in cannot be deleted or defined and is assigned to administrators only. The purpose of this universe is to provide administrators with access to all data. This universe is not even listed in the
    page of the universes.
Users can be assigned to more than one universe. In this case,
All My Universes
is available in the
view and in the
All My Universes
shows data from all users universes all together. For more information, see Article ID: 113376: Users with read access in team center can't see "all my universes" view.
Two different use cases are available for creating universes:
  • Create a universe for navigation
    - Create universes for navigation to provide users with a series of pre-configured filtered environments. Users can switch between the environments to view different areas of a complex environment quickly.
  • Create a universe for security
    - Create universes for security to restrict the components of the environment that an individual user can view. We recommend that you base the content of a security universe on transaction paths. Create custom attributes at boundaries that enable analysts to identify the continuation of the path. If your environment uses domains, the agentDomain attribute is populated by default. Use the agentDomain attribute as a filter condition to create a universe that matches the permissions restrictions of the specified domain.
Create a Universe
When defining a new universe, you can grant different rights to users and user groups. The rights to access the universe, select metric sources, map components and manage modules.
Follow these steps:
  1. Consider the content that you want to define in this universe.
  2. Select
    in the left pane and then select
    New Universe
    A dialog pane opens.
    The definitions added to a tab are propagated to the corresponding individual part of the application. For example, the definitions added to the Map components are applied to the Map. The definitions added to the Metric Sources are applied to the Metric Browser. Other parts of the application are not affected.
  3. Assign a name to the new universe.
  4. (Optional) Add a description for the universe.
  5. In the
    view, you grant different access rights to this universe to users and/or user groups.
    1. Select the right that you want to grant:
      • Read:
        Lets users see the components that are selected in the universe.
      • Edit:
        Lets users modify the components that they select in the universe and add attributes or rules to the map components. Edit also includes Read rights.
      • Manage:
        Lets users modify the access rights to the universe. Administrators use Manage right to delegate assigning access rights to other users. Manage also includes Read and Edit rights.
    2. Select the user or user group you want to grant the right to from the dropdown list.
    3. Click
      Add User
      Add Group
      to add the selected user or user group to the universe.
    4. (Optional) Select a different right and user or user group and add them to the list.
  6. In the
    Metric Sources
    • The
      Filter Metric View by Map components
      option filters metric trees in the metric browser by map. Default value:
      (the filter is applied by default). Select the checkbox to disable the filter.
    • Select
      All metric sources
      , including future components. If you select this option, the universe contains all map sources (agents) and nothing is filtered out.
    • Customize the metric sources by selecting a subset of individual agents and/or adding a regular expression. Regular expressions are based on hostname|processname|agentname. Examples of expressions:
      • myhost\|.* - selects all agents running on host “myhost”. The pipe character is escaped with a backslash as it is a regex control character.
      • usnye.* - selects agents from all host with the prefix “usnye”.
      • .*\|.*\|dmn13t.* - selects all agents with the prefix “dmn13t”.
      in the dialog at the bottom of the page to see a preview of the sub-tree for the selected agents.
    The metric sources of the universes created before version 20.11 must be reconfigured.
  7. In the
    Map Components
    view, select one of these actions:
    • Map all components (including future components). If you select this option, the universe contains all map components and nothing is filtered out.
    • Use the
      Metric Sources
      filter. If you select this option, the universe contains all map components that are generated by agents that are selected by the
      Metric Sources
    • Customize the filter. Define a map filter to select the required map components. This filter is the same as the one in the
      For more information about the experience node, see Monitor Performance Using Experience View.
  8. In the
    Management Modules
    view, select one of the following:
    • All items (including future items).
    • One or more items from the list.
  9. The
    view is generated after saving the universe. This view contains an overview of the universe definitions. The overview includes the number of components in various parts of the application (for example, map and metric view).
  10. Select
    As an administrator, you can also create a universe directly from the Map in the 'Enterprise' Universe. Define the map filters and select
    Save as Universe
    in the top-right corner to save the current filtered map nodes as a universe.
Modify a Universe
Follow these steps:
  1. Select
    in the left pane.
  2. Identify the universe that you want to modify and select
  3. Follow the steps that are described in the Create a Universe section.
Delete a Universe
Follow these steps:
  1. Select
    in the left pane.
  2. Identify the universe that you want to remove and select
  3. Confirm the deletion.
Configure Universe Security
In each Universe, users are assigned individual privileges per management module to edit alerts, calculators, and metric groups. The Power User role, users, and user groups must be given permission to view or create alerts, calculators, or metric groups for a management module. The Power User is able to manually start transaction trace sessions. The Tenant Administrator has all privileges. Privileges must be assigned to each single management module in a Universe. The privileges are in effect only when viewing the specified Universe. Here are the privileges by permission type:
  • read:
    Allows the Power User, user, or assigned user group to see the management module alerts, calculators, and metric groups.
  • write:
    Allows the Power User, user, or assigned user group to see and modify management module alerts, calculators, and metric groups.
  • manage:
    Allows the Power User, user, or assigned user group to see and modify the management module alerts, calculators, metric groups, and users. Users with
    privilege can also add management modules to the Universe.
A user with
access to the universe where the management module is located, or the Tenant Administrator must explicitly grant the management module the
Metric Source
path. This path allows all users to view the alarm and calculator metrics in the Metrics Tree.
We strongly recommend these settings to ensure that users have the correct access to management modules settings:
  • Do not assign users to a Universe with a
    Management Module scope
    setting of
    All Items
  • Explicitly add
    Management Modules
    as part of the scope to all Universes
    Enterprise Universe. Enterprise is a special universe only available to the Tenant Administrator.