Map Layers

As an administrator, you can quickly navigate through the map layers to identify the root cause of performance issues. Switch between layers in the map to view performance issues that are caused by application components, infrastructure components, or Application Performance Management (APM) components. Apply more filters to view specific types of components within the layers. Refine the number and types of components into easy to use groups (Universes).
apmdevops106
As an administrator, you can quickly navigate through the map layers to identify the root cause of performance issues. Switch between layers in the map to view performance issues that are caused by application components, infrastructure components, or Application Performance Management (APM) components. Apply more filters to view specific types of components within the layers. Refine the number and types of components into easy to use groups (Universes).
 
 
Overview
Map layers overlay different types of components from the environment onto the map. The map only shows nodes and connections for components that are within the selected layer. Connections between components from different layers are called cross-layer connections. Components that have cross-layer connections to components within the selected layer are displayed in the Component View on the right. For example, when you select a servlet component on the map, Component View shows the servlet properties, together with properties for the agent that monitors the servlet.
APM automatically adds cross-layer connections between agents and the application components that the agents monitor.
Use Map Layers
Switch between map layers to view components from a specific layer. Select a component in the map and view the cross-layer connections in the Component View. 
 
Follow these steps:
 
  1. Select a map layer from the drop-down list. Choose from the following layers:
    •  
      Application Layer
      Shows application components that the APM agents monitor. This layer corresponds to the map components from previous versions of APM.
    •  
      APM Infrastructure Layer
      Shows APM components, such as agents and collectors.
    •  
      Infrastructure Layer
      Shows hosts, docker instances, and other physical components. This layer contains information from  the Infrastructure Agents and their extensions. The infrastructure layer also collects information from integrations, for example, Unified Infrastructure Management (CA UIM).
      On-premise CA APM lets you integrate components from other systems into the infrastructure layer using the REST API. CA UIM uses that REST API to integrate with On-premise CA APM so that On-premise CA APM shows hardware components.
  2. Click a component on the map to open Component View.
  3. Switch between the tabs in Component View to see properties for both the selected component and connected components from other layers.
Apply Filters in the Map Layers
A filter is a list of attributes and required values that lets you view specific components in the map. Apply a filter to view all components from the filtering layer that match the filter attributes. If you switch layers, components that have cross-layer connections to the filtered components remain visible in the map.
 
Follow these steps:
 
  1. Select a map layer and click on a filter attribute from the list of attributes.
     The filter does not let you combine attributes from different layers, thus all attributes in a filter must come from a single layer. If you switch the map layer, you can only add attributes from the original layer. This layer is called the filtering layer.
  2. Switch between the map layers to view components that have cross-layer connections to the filtered results in the filtering layer.
 
Example:
The following diagram shows an unfiltered map that contains multiple cross-layer connections:
map layers1
map layers1
 
Action:
On the APM Infrastructure Layer, you set the filter to return agents with ‘ABC’ and ‘XYZ’ in the names. 
 
Result:
The following diagram shows the filtered results for each map layer:
maplayers2
maplayers2
 The APM Infrastructure Layer does not show collectors or EM databases when the filtering layer is the Application Layer. Collectors and EM databases do not have cross-layer connections to application components. Only agent type components have cross-layer connections to the Application Layer.
Apply Universes in the Map Layers
After you set a filter to select specific components, you can save the filter as a universe. Authorize users to access all components in the universe, including components that have cross-layer connections to the selected components. For more information about configuring universes, see Configure Universes.
The following examples show possible uses of filters in the map layers.
 
Example 1: Capture Full Transactions That Pass Through a Specific Domain
This universe contains complete monitored transactions that pass through a selected domain, including inferred backend components and business transaction nodes. This universe also contains all agents that are monitoring the application components.
Follow these steps:
 
  1. Select the 
    Application Layer
     as the filtering layer.
  2. Click 
    Add Filter
     and select 
    FOLLOW TRANSACTION PATH.
     
  3. Select
     agentDomain 
    from the list of attributes.
  4. Enter the 
    agentDomain 
    name
     
    in the
     Filter 
    to
     
    find transactions for that domain.
 
Example 2: Grant Admin Access to All EM Collectors, EM Databases and Agents From a Specific Domain
This universe contains the required components from the APM Infrastructure Layer, together with application components that agents monitor within the specified domain. The results do not show inferred backend or business transactions because these transactions are not monitored by agents.
Follow these steps:
 
  1. Select the
     APM Infrastructure Layer 
    as the filtering layer.
  2. Click 
    Add Filter
     and select the 
    agentDomain
     attribute.
  3. Enter the 
    agentDomain 
    name
     
    in the
     Filter.
     
  4. Click
     + 
    to add a new filter item and select
     Add new filter group.
     
  5. Select
     Type 
    from the attribute list.
  6. Select all attribute values except 
    AGENT
    , for example, 
    EM_COLLECTOR
    EM_DATABASE
    , and others.