Configuring retention period for resource history

Agile Service Manager retains historical topology data for a default period of 30 days. You can increase this to a maximum of 90 days by increasing the 'time to live' (TTL) value.

Before you begin

CAUTION:
The performance and scalability of Agile Service Manager is affected by the number of resources managed, the amount of history present for each resource, and the ingestion rate. If you increase the retention period for historical resource data from the default of 30 days (up to a maximum of 90 days), your system performance (when rendering views) may deteriorate, if as a result of this increase resources have in excess of 25,000 historical entries.

About this task

The retention period for historical resource data is configured via the HISTORY_TTL configuration property.

When a resource or edge in Agile Service Manager is deleted, it will no longer appear in the UI. Historic representations of the resource or edge, however, are retained and can be accessed in the UI history timeline until the history TTL limit has been reached, after which the data is deleted.
Note: Unless explicitly deleted, live resources remain current and the TTL limit does not apply to them.

For an illustration. see the example section.

Procedure

Edit the configuration file

  1. Open the /opt/ibm/netcool/asm/.env file using an appropriate editor.
  2. Edit the HISTORY_TTL setting. Enter the values in hours.
    Change the TTL value from the default of 720 (30 days) to any value up to 2160 (90 days).
  3. Restart Agile Service Manager: 
    $ASM_HOME/bin/asm_start.sh

Example

In the following example scenario, the default TTL value of 30 days (720 hours) applies.
Table 1. TTL example for the 'sprocket' resource
Date Action Topology view Historical data
01-January-2019 sprocket resource created sprocket resource visible in current and history History is current resource
01-March-2019 sprocket resource modified sprocket resource visible in current and history History has both current and previous resource
31-March-2019 TTL expires for historic resource created on 01-March sprocket resource visible in current and history History is current (modified) resource only
01-May-2019 sprocket resource deleted sprocket resource visible in history only History still contains deleted resource
31-May-2019 TTL expires for historic resource created on 01-May sprocket resource not visible in current or history No history remains