What properties control the pruning of Team Center map data to prevent the APM DB from growing too large.

Document ID : KB000016066
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

What properties control the pruning of Team Center map data to prevent the APM DB from growing too large?

Environment:
APM 10.x
Answer:

The 2 relevant properties to be set in the IntroscopeEnterpriseManger.properties file are:

introscope.apm.data.preserving.time (defaults to 365 DAYS): This property controls pruning of the legacy appmap data and the new Team Center map data. This task uses APM DB function prune_apm_data and runs at the time controlled by property introscope.apm.pruning.cron.trigger.expressionIn APM releases 10.0-10.3 this property is also used to prune the appmap_states_yyyymmdd tables (Team Center alert status changes)

introscope.apm.alert.preserving.time (defaults to 62 DAYS): This property is now used in APM release 10.5 and above to enable independent pruning of just the appmap_states_yyyymmdd table partitions. This task has no runtime control property and executes when the EM starts & then every 24 hours/daily after that. It uses DROP TABLE commands to remove the old partitions.

When using a Postgres APM DB execution times for the above tasks can be viewed in the postgres log (assuming the appropriate log_statement level is set in the postgresql.conf file e.g. log_statement = 'mod')

Additional Information:

The new property introscope.apm.alert.preserving.time is hidden in APM 10.5 but will be fully documented in the next release APM 10.7.