Skip to content
CA Application Performance Management - 10.0
Documentation powered by DocOps

Configure the Application Triage Map

Last update January 4, 2018

The following section explains how to configure the Application Triage Map.

Note: We recommend that you use APM Team Center Workflow for enhanced features and improved performance.

The application triage map presents a graphical visualization of the components that make up your application, showing application health and errors. This map is automatically generated from performance and analysis of Introscope metrics, errors, and events. It presents applications in the business-centric terms that you’ve defined. The application triage map enables you to instantly grasp the structure of and relationships between the applications in your environment in a visual manner to help you identify and triage current and emerging problems.

For more information about the appearance and use of the application triage map, see Triage with the Workstation.

Introscope agents detect business transactions and frontends and detect their dependencies. Agents then report this information as data to the Enterprise Manager, which stores the data in the APM database and sends the data to the Workstation. The Workstation displays the data as the application triage map in the Map tab.

You can configure:

  • whether or not agents collect application triage map data.
  • the rate at which Introscope samples frontend or business service data for the purpose of drawing the map. See Transaction sampling.
  • how long application triage map data is stored in the APM database. See Map element aging.
  • whether or not, and how often, application triage map data is pruned from the APM database. See Application triage map data pruning.

Transaction Sampling

Introscope uses a technique known as transaction sampling to provide data for the application triage map display. After an agent is started, Introscope takes (by default) the first hundred transactions to draw an initial map of a frontend or business transaction and its dependencies. Subsequently, it gradually reduces the number of transactions it samples until it reaches a level where only every tenth transaction provides continuing data support to the map. After each ten thousand transactions, this pattern repeats.

You can adjust the sampling rate by editing these properties in the IntroscopeAgent.profile:

  • introscope.agent.tracer.sampling.maxrate
  • introscope.agent.tracer.sampling.initial.period
  • introscope.agent.tracer.sampling.reset.period

For information about editing properties in IntroscopeAgent.profile, see the Java Agent or Microsoft .NET Agent (depending on your environment).

Be aware that adjusting these properties to increase the number of transactions supporting the map display may affect overhead.

Configure Map Element Aging

When data for a connection ages out or is pruned from the APM database, the agents rediscover frontends and business services and their dependencies. The Workstation displays this data on the application triage map.

After enabling agents to collect application triage map data, you can configure how often agents perform this data collection. For example, you can configure agents to collect application triage map data:

  • Once every 24 hours if there are frequent changes to the environment.
  • Once a week if there are infrequent changes to the environment.

You can also configure the time period over which the Enterprise Manager delivers data in the map. For example, data discovered by an agent can appear for a week or a month. The time period is based on two map time range properties: "aging time" and the "window time."

Aging is a characteristic of application triage map elements. When Introscope no longer receives data for a frontend or business transaction, the map element is aging. Aging time is the amount of time during which Workstation continues to display the element in the application triage map. When this time has expired, the element is removed from the agent cache and the element appears in the application triage map as aged. The aging time is set in the property. The default is one day.

The time window is the amount of time the Workstation displays an aging element before the element disappears from the map altogether. This option is set in the property. The default is three days.

For example, with default settings:

ApplicationA is a frontend in the application triage map and a dependency exists with ApplicationB. Agents continue to report data for ApplicationB and ApplicationB appears in the map display normally. When data ceases to be reported from ApplicationB, the clock starts on both the aging time and the window time. After one day, the map node for ApplicationB will appear as aged. After three days, the ApplicationB map node disappears from the map.


  • The timeWindow includes the period of agingTime.
  • If the timeWindow and agingTime are set to the same duration, the map elements cannot be displayed as aged. They disappear when the timeWindow period ends.
  • If you set timeWindow to a value greater than agingTime, aged map elements disappear when the agingTime period ends.
  • For agingTime and timeWindow, choose a value that is based on how often your organization adds and modifies applications. The value can increase or reduce overhead for agents and the Enterprise Manager. If you set lower values, then the map displays application dependencies on a real-time basis. If you set higher values, then the map displays current application dependencies.
Important! In a clustered environment, any changes to the agingTime or timeWindow default property values must also be applied to the MOM and on all Collectors.

Follow these steps:

  1. Open the file in the <EM_Home>/config directory.
  2. If you are changing the value for
    1. Stop the agents.
    2. Shut down the Enterprise Manager.
    Important! If you change the value for the property, see Implications of reducing the application triage map aging time setting.
  3. Configure the property. The default is one day. The value cannot be less than 1 minute.
  4. Configure the property. The default is three days. The value cannot be less than 1 minute.
  5. Save and close the file.
  6. If you changed the property, restart the agents.
  7. Restart the Enterprise Manager.
  8. View the Enterprise Manager log file messages for the map data aging properties in the <EM_Home>/logs directory. For example:

    11/23/09 12:02:13 PM PST [INFO] [Manager] [ The APM Data  property : set to value : [ PropertyWithTimeUnit : 1 Min]]

Implications of Reducing the Application Triage Map Aging Time Setting

If you plan to reduce the value of the property in the file, CA Technologies recommends you clean the application triage map data to avoid unexpected effects on historical data. Reducing the aging time means a smaller data sample appears in the map display, and this may result in a misleading display based on data in the APM database, because of the way agents report data to the Enterprise Manager. Cleaning the data from the database prevents this problem.

To clean the data, you must use a PostgreSQL client. Such a client can be downloaded from the PostgreSQL site at

To use the PostgreSQL client to clean the database:

  • Execute the following SQL statement:

    truncate apm_edge;

    Increasing the value of the property has no such unexpected effects. Cleaning the database is only necessary if you want to decrease the value of the property.

How Aging-Related Properties Affect the Historical View

When viewing historical data with the application triage map, keep in mind these concepts:

    • Regardless of how you set the beginning and end points of your historical time period, the data displayed on the application triage map will always span at least the period of time set in the property. For example:
      • If you set the beginning and end dates of the historical period to a 10-day span, but is set to 3 days, the map will display data for the entire 10-day span.
      • If you set the beginning and end dates of the historical period to a 2-day span, but is set to 3 days, the map will still display 3 days worth of data, with the 3-day period ending at the same time as the ending of the 2-day period. Whatever the property is set to is the minimum time period for what the map displays, even if the manually set historical period is less.
    • The aging behavior of map elements will follow the period of time set in the property as if that aging time occurs at the end of the historical window. For example:
      • If is set to 1 day, and your historical time period is set to 10 days, the map element will be displayed as aged if no agent reported this element for the final (1) day of the period.
Was this helpful?

Please log in to post comments.