Configure Experience View

As an administrator, configure Experience Cards in Experience View. Configure cards so that analysts can easily view the most business critical components that affect the end-user experience.
As an administrator, configure Experience Cards in Experience View. Configure cards so that analysts can easily view the most business critical components that affect the end-user experience.
Experience View
Administrators perform the following tasks:
  • Configure the universe.
  • Add a new Experience Card
  • Edit an Experience Card.
  • Share an Experience Card
Experience View Cards
Learn how to build an Experience Card in the Experience View. Configure your Experience Cards so that analysts have their Universe divided into meaningful groups.

Configure Universe
Before you can configure the Experience View for a user, assign at least one universe to the user.
All My Universes are available in
view for the administrators only. For other users, All My Universes View is available in
view, if more than one universe is assigned.
More information:
Add New Experience Card
Out of the box, for an Enterprise Manager, the system creates two Experience Cards for each existing universe. Experience Cards for Applications have two drill-down levels with the
attributes. Experience Cards for Services have two drill-down levels with the
Business service
attributes. As an administrator, create, update, or delete any number of customized Experience Cards for analysts.
If you add a new universe or if you connect a new provider, Experience Cards are not automatically created. The automatic creation of Experience Cards is only a part of an installation or upgrade.
Follow these steps:
  1. Open Experience View and ensure that you are in the top-level view.
  2. Click the + button to add a new Experience Card.
    The + button is only available at the top-level view of the Experience View.
  3. Select a universe.
  4. Use the entire universe or apply a filter.
  5. Select the attributes. Experience Cards are grouped by attributes. The drill-down levels of the Experience Card correspond with the number of attributes that you select.
    We recommend using three to four levels of attributes.
  6. Select a default chart type:
    • Histogram
    • Average Response Time
    • Transaction Volume
  7. Name the card
  8. Select the box
    Make this Experience Card public
  9. Click
The administrator can now see the Experience Cards in Experience View.
An error message shows when you attempt to display more than 500 business transactions in live mode or more than 50 business transactions in historical mode. Experience View limits the number of displayed business transactions for performance reasons.
More information
: No Metric Data in Experience View.
Edit Existing Experience Card
At the top level of Experience View, you can edit Experience Cards, both the default cards and user-defined cards.
Follow these steps:
  1. Click the expand icon in the bottom-right corner of the card.
  2. Click
    Edit Card.
  3. Change the card settings as required.
  4. Click Save.
Delete Experience Card
At the top level of Experience View, you can delete Experience Cards, both the default cards and user-defined cards.
Follow these steps:
  1. Click the expand icon in the bottom-right corner of the card.
  2. Click
    Edit Card.
  3. Click
    Delete Card.
  4. The card is removed for all users who have access.
Share Experience Card
You can share an Experience Card with a user within an existing universe.
Follow these steps:
  1. Check that the user has access to the universe.
  2. On the Experience Card, select
    Make This Card Public
    The card appears in your list of cards.
  3. Send the Experience Card link to the user.
    You can share a private Experience Card with a user from the same universe. The user can temporarily view the private card.
Use Propagator to Group Experiences using Attributes
Experience View lets you organize experiences (experience nodes) into cards that are based on attributes. You can use the Propagator to expand the selection of attributes for grouping experiences. The Propagator copies attributes from adjacent components that are directly connected to an experience. The Propagator adds attributes to experience vertices (the left-most nodes). The Propagator copies the attributes from the directly connected vertices (from the next to the left-most) from the APPLICATION layer. The attributes are propagated up to the experience based on rules.
You can define blacklist and white list of attributes to control what attributes the Propagator copies. Multiple components can be connected to a single experience. In this situation, when the same attribute is defined several times, the attribute is propagated only when all occurrences of that attribute have the same value.
The Propagator can gather and send attributes between map layers. You can configure the Propagator to collect attributes from specific map llayers. For example, have the Propagator copy the IP address from the connected host.
Or you can organize your experiences based on Infrastructure-layer Docker and host attributes.
The value contains a comma/semicolon separated list of layers to copy from. These are default values of all propagator's settings: introscope.apmserver.atc.propagator.blacklist=CUSTOM\..*;DECORATED\..*;HIDDEN\..*;Name;Hostname;Agent;AgentDomain;Experience;IsExperience introscope.apmserver.atc.propagator.whitelist=.*Owner introscope.apmserver.atc.propagator.crosslayer=
Configure Propagator Settings
Define the attributes that you want to propagate to your experiences using RegEx syntax on the attribute names. Identify the attribute source and configure cross-layer propagation. You define these global propagation rules by editing the Propagator-related properties.
Follow these steps:
  1. Define and identify the attributes that you want to propagate. Here are the available attribute sources:
      Includes attributes that the agent defined when monitoring the component.
    • CUSTOM
      Contains attributes that you manually created in the UI or defined in the REST API.
      Groups attributes that you created using attribute rules. Attributes that are propagated to experiences are always decorated. These attributes can be overwritten by attribute rules, the REST API, or manual changes in the UI.
  2. Navigate to the
    directory of the appropriate Enterprise Manager.
    Depending on your deployment, the Propagator runs on one of these Enterprise Managers:
    • Standalone Enterprise Manager
    • MOM in a cluster deployment
      If you have multiple clusters, configure only one MOM. The Propagator runs only on one instance -- on the "main" Enterprise Manager.
    • Enterprise Team Center Enterprise Manager in an Enterprise Team Center deployment
  3. Open the
    file in a text editor.
  4. Configure the
    property to block attributes.
    • introscope.apmserver.atc.propagator.blacklist
      This property specifies black-listed attributes.
    • Default:
      The default blacklist does not propagate these attributes:
      • Custom or decorated attributes
      • Name
      • HostName
      • Agent
      • AgentDomain
      • Example:
    • Use a white list to propagate certain attributes
      Configure blah...
    • introscope.apmserver.atc.propagator.whitelist
      Specifies the white-listed attributes.
      The default whitelist propagates the
    This example shows propagation of the
    attributes to an experience from the connected servlet.
    • Tier
      is not propagated because the blacklist disables propagation of custom attributes.
    • HostName
      is not propagated because it is also blacklisted.
    • servletMethod
      is not propagated because the servlets have different values.
    • Owner
      is propagated because it does not conflict with MyServletB.
    • servletClassName
      is propagated because both servlets have the same values.
  5. Configure cross-layer attribute propagation. Specify the map layers in the
  6. Values:
    To enable propagation from multiple map layers, separate each layer value with a comma.
  7. Default:
    The default value is an empty string, which means cross-layer propagation is disabled. 
  8. Example:
    In this example, the Propagator is set up to pull attributes from the Infrastructure Layer:
  9. Save and close the file.
  10. Restart the Enterprise Manager.
Data Clamps
The historic mode data clamp is 50 experiences. The live mode data clamp is 500 experiences. Experiences are business transactions or application entry points. If you select a time range in historic mode within the last 24 hours, the data clamp for live mode (500 experiences) is applied. The last 24 hours are covered by cached data.