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.
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. Select the + button to add a new Experience Card.
  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. Or, group by one attribute to monitor a specific group of components. For example, Owner = Joe.
  6. Select a default chart type:
    1. Histogram
    2. Average Response Time
    3. Transaction Volume
  7. Name the card
  8. Select the box
    Make this Experience Card public
  9. Select
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. For more information, see 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. Select the expand icon in the bottom right corner of the card.
  2. Select
    Edit Card.
  3. Change the card settings as required.
  4. Select
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. Select the expand icon in the bottom right corner of the card.
  2. Select
    Edit Card
  3. Select
    Delete Card
    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. Select the expand icon in the bottom right corner of the card.
  3. Select
    Edit Card
  4. Select
    Make this Experience Card public
  5. Select
    The card appears in your list of cards.
  6. 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.
Experience View lets you organize experiences (experience nodes) into cards that are based on attributes. To expand the selection of attributes for grouping experiences, use the Propagator. The Propagator copies attributes from adjacent components that are directly connected to an experience. These attributes are propagated up to the experience based on rules. If multiple components are connected to a single experience and the same attribute is defined several times, the attribute is propagated only if all occurrences of that attribute have the same value. The propagator can also gather and send attributes from other map layers. For example, with this cross-layer propagation, you can organize your experiences based on docker and host attributes from the Infrastructure Layer.
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.
Follow these steps:
  1. Define and identify the attributes that you want to propagate. The available attribute sources are as follows:
      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. Use a white list to propagate certain attributes or use a black list to block attributes. Define these global propagation rules by editing the following properties that are found in the
    • introscope.apmserver.atc.propagator.blacklist
      Specifies the black-listed attributes.
      The default blacklist does not propagate the following attributes:
      • Custom or decorated attributes
      • Name
      • HostName
      • Agent
      • AgentDomain
    • introscope.apmserver.atc.propagator.whitelist
      Specifies the white-listed attributes.
      The default whitelist propagates the
    The following 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.
  3. To configure cross-layer attribute propagation, open the
    file from
    directory. Specify the map layers in the
    <blank> The default value is an empty string, which means cross-layer propagation is disabled.
    To enable propagation from multiple map layers, separate each layer with a comma.
    In the following example, the propagator is set up to pull attributes from the Infrastructure Layer:
Data Clamp
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.