Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Automatically purging invocation history

Updated on April 6, 2022

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 service/MonitorInstanceTTLMins 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.

  1. To configure how long to keep invocation history, create the service/MonitorInstanceTTLMinswith owning ruleset Pega-IntegrationEngine.
    For more information, see Creating a dynamic system setting.
  2. To enable and configure the agent, in the header of Dev Studio, enter Pega-IntegrationEngine.
  3. In the search results, in the Agents row, click Pega-IntegrationEngine to open the pzCleanupServiceMonitorInstances agent.
  4. On the Schedule tab, in the Interval (sec) field, enter the frequency, in seconds, that you want the agent to run.
  5. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us