The following section explains how to configure the Application Triage Map.
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:
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:
Be aware that adjusting these properties to increase the number of transactions supporting the map display may affect overhead.
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:
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 introscope.apm.data.agingTime 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 introscope.apm.data.timeWindow 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.
Follow these steps:
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 : introscope.apm.data.agingTime set to value : [ PropertyWithTimeUnit : 1 Min]]
If you plan to reduce the value of the property introscope.apm.data.agingTime in the IntroscopeEnterpriseManager.properties 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 http://www.pgadmin.org.
To use the PostgreSQL client to clean the database:
Execute the following SQL statement:
Increasing the value of the property introscope.apm.data.agingTime has no such unexpected effects. Cleaning the database is only necessary if you want to decrease the value of the property.
When viewing historical data with the application triage map, keep in mind these concepts: