Application Triage Map Data and Objects

22
apmdevops106
By default, Application Triage Map topology data is disabled. Metric data are displayed on the Leaf Nodes.
2
2
Application Triage Map Data Clamping
To control data flow to the application triage map for the purpose of assuring good performance, Introscope uses a threshold, set using the property introscope.apm.query.max.results (found in
APMEnterpriseManager.properties
), to clamp the amount of data the Workstation will attempt to display on the map. When you select a tree node or attempt to unroll a map element that would exceed this threshold, you see a message stating "The map is too large to display." You can adjust this threshold by adjusting the value of the property.
Please note that the
introscope.apm.data.obsolete.time
property is deprecated from APM 10.7 SP4 onwards.
Adjusting the value for the introscope.apm.query.max.results property may affect Workstation performance.
For more information about this property, see introscope.apm.query.max.results.
To edit the application triage map display threshold:
  1. Open the
    APMEnterpriseManager.properties
    file in the
    <EM_Home>/config
    directory.
  2. Shut down the Enterprise Manager.
  3. Find the introscope.apm.query.max.results property and adjust its value.
  4. Save and close the
    APMEnterpriseManager.properties
    file.
  5. Restart the Enterprise Manager.
Configure Application Triage Map Data Pruning
The application triage map data in your APM database can grow over time. Excessive data in the APM database can affect Enterprise Manager retrieval of application triage map data as well as Workstation and Enterprise Manager performance. You can prune application triage map data to avoid collecting excessive map data in the APM database.
If you enable application triage map data pruning on the APM database, configure the setting for only one Enterprise Manager in a cluster. However, it is recommended that you enable application triage map data pruning on the MOM.
You can configure how long map data remains in the database until it is pruned and how often you want to scheduling the pruning to occur. Map data pruning is controlled by a scheduler, which can be configured to prune data, on a daily, weekly, or monthly basis.
You cannot configure a Collector for application triage data pruning. If you set the
introscope.apm.pruning.enabled
property to
true
for a Collector, errors are returned.
If application triage map data is pruned while a user is viewing the map, the pruned data remains on the map until the user changes the map time range, which triggers the map to be redrawn.
If you allow more than one Enterprise Manager to prune the database, multiple pruning processes compete for database access and create a database deadlock.
Follow these steps:
  1. Open the
    IntroscopeEnterpriseManager.properties
    file in the
    <EM_Home>/config
    directory.
  2. Shut down the Enterprise Manager.
  3. Verify that the
    introscope.apm.pruning.enabled
    property is to
    true
    .
    This property enables the agents to prune application triage map data.
    If you reset
    introscope.apm.pruning.enabled
    from
    false
    to
    true
    , restart the Enterprise Manager for this property to take effect.
  4. (Optional) Configure the following properties:
    Note:
    Set the value of the introscope.apm.data.preserving.time property low to manage the volume of application triage map data in your environment, or exceptions can display. To prevent exceptions, verify that your environment is tuned in accordance with the application usage before you install the APM SOI connector. If you still see exceptions, increase the value for the introscope.apm.query.max.results property in the APMEnterpriseManager.properties file.
  5. Save and close the
    IntroscopeEnterpriseManager.properties
    file.
  6. Restart the Enterprise Manager.
    When the Enterprise Manager starts, you can go
    <EM_Home>/logs
    to review the Enterprise Manager log file messages associated with the map data pruning properties. For example:
    11/23/09 12:02:13 PM PST [INFO] [Manager] [ The APM Data property : introscope.apm.pruning.enabled set to value : true] 11/23/09 12:02:13 PM PST [INFO] [Manager] [ The APM Data property : introscope.apm.pruning.cron.trigger.expression set to value : 0 0 6 * * ?]
Configuring Obsolete Time on Application Triage Map Objects
CA APM refers to Application Triage Map objects and the relationships between them with the terms
edge
and
vertex.
The APM database stores data about these objects.
Over time, when connections between the Enterprise Manager and the monitored application are lost, edge objects “age out” according to two factors:
  • The value of the property
    introscope.apm.data.preserving.time
  • Rules as described in the table below
When edge objects age out, all associated objects are classified as
obsolete
if they are not used in any other active edge object. The Application Triage Map displays the elements associated with these obsolete objects as "greyed out" to make it clear they represent old, not current, data.
These "aged" objects remain in the APM database and are not automatically deleted. Objects are deleted only when the Application Triage Map Pruning process occurs, based on the properties that are set for pruning. The Pruning stored procedure physically deletes the objects based on pruning rules, which differ from Obsolete rules. For more information about pruning, see Configure Application Triage Map Data Pruning.
Rules for Application Triage Map object aging
Object
Conditions
Edge
(database table apm_edge)
An Edge is considered to be obsolete when its update date is older than the value in the
introscope.apm.data.preserving.time
property.
Vertex (database table apm_vertex)
A Vertex is considered to be obsolete if it is only referenced by obsolete Edges and no other Edges in the Application Triage Map.
Owner (database table apm_owner)
An Owner is considered to be obsolete if it is only referenced by obsolete Edges and no other Edges in the Application Triage Map.
Agent (database table apm_agent)
An Agent is considered to be obsolete if it is only referenced by obsolete Vertices in the Application Triage Map.
Application Triage Map Time Aging Properties
You can return requests for obsolete objects from the database by configuring the Time Aging properties for the application triage map. If a time is not configured, then any request pointing to a time point within the period (introscope.apm.data.preserving.time + introscope.apm.data.agingTime) can specify the object as obsolete.
The Default values are:
  • introscope.apm.data.preserving.time
    Default: 365 DAYS
  • introscope.apm.data.agingTime
    Default: 1 DAY
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.
Example
To retrieve information on the obsolete objects, run the query Web Services APIs on November 1at 0800h and 1500h, and on November 2 at 1000h. This query provides the following results for each request:
  • Get obsolete objects at November 1 8:00
    Identifies obsolete objects older than 300 days at November 1 8:00. Any objects older than introscope.apm.data.preserving.time + introscope.apm.data.agingTime are not returned.
Configuring Application Triage Map Time Aging Properties
The application triage map objects are marked obsolete based on the introscope.apm.data.preserving.time property. If the introscope.apm.data.preserving.time uses the default value 365 DAYS, then objects older than 365 days become obsolete.
Follow these steps:
  1. Shut down the CA Enterprise Manager.
  2. Open the IntroscopeEnterpriseManager.properties file in the <
    EM_Home
    >/config directory.
  3. Verify that the introscope.apm.data.preserving.time property is uncommented and a value is set other than the default value of 365 days.
    Specify HOURS or DAYS; 24 hours or 1 day is the minimum.
  4. Save and close the IntroscopeEnterpriseManager.properties file.
  5. Restart the Enterprise Manager.
    The obsolete time property is configured.
  6. View the message logs in the
    <EM_Home>
    /logs directory.