If you are monitoring Service REST rules, the invocation history can become large and take up space in the database. You can purge invocation history automatically to delete data that you no longer need from the database.
To automatically purge invocation history, you use a dynamic system setting and an agent
that must be enabled and configured. The
dynamic system setting specifies how old, in minutes, the invocation history must be for the
pzCleanupServiceMonitorInstances agent to delete it. For example, if
the setting is 70 minutes, when the agent runs, it removes all invocation history instances
that are older than 70 minutes.
By default, the pzCleanupServiceMonitorInstances agent is not enabled.
The interval configured for how often the agent wakes up and runs is not the same as the number of minutes to keep invocation history. For example, if the agent is configured to run every 15 minutes and the number of minutes to keep invocation history is set to 10 minutes, the agent runs every 15 minutes and deletes invocation history that is older than 10 minutes.
Perform one of the following actions:
Configure how long to keep invocation history by performing the following actions:
Enter a short description that identifies the setting.
In the Owning Ruleset field, enter Pega-IntegrationEngine.
In the Setting Purpose field, enter service/MonitorInstanceTTLMins.
Click Create and open.
In the Value field, enter the number of minutes to keep invocation history before deleting it.
Enable and configure the agent by performing the following actions:
Click the pzCleanupServiceMonitorInstances agent to open the agent schedule.
In the Interval field for the pzCleanupServiceMonitorInstances agent, enter the frequency, in minutes, that you want the agent to run.
Select the check box in front of the agent name.
Previous topic Immediately purging Service REST invocation history