Event Log Cleanup

Overview

This page describes how to schedule and configure automatic cleanup of the event log stored in the content repository.

Purpose

Configure a scheduled job to remove old or excess event log entries from the repository, maintaining performance and storage efficiency.

Event Log Background

The Event Bus logs events in the repository. For example, when a workflow action occurs, the system posts a workflow event to the event bus, which is then persisted in the event log. Over time, the event log can accumulate millions of entries. Regular cleanup is required to prevent performance degradation.

Configuring the Event Log Cleanup Job

You can schedule automatic event log cleanup by configuring the event log repository job with the repository scheduler in the console. The configuration node is located at:

/hippo:configuration/hippo:modules/scheduler/hippo:moduleconfig/system/EventLogCleanup

Configure the following properties:

• maxitems
  Sets the maximum number of items allowed in the event log. For typical use, set this to 50000. Use -1 to disable the maximum item limit.
• minutestolive
  Defines how long (in minutes) to retain items after creation. The recommended value is -1, which disables age-based truncation.

These recommended values are included by default when you create a project using the Maven archetype.

The cleanup job runs according to the cron expression configured in the cron trigger node below the job node. When triggered, the job reduces the event log to maxitems if the number of entries exceeds the limit, and removes any items older than the minutestolive threshold.

Adjusting the Cleanup Schedule

To change the cleanup schedule, update the cron expression on the trigger node. Refer to the Quartz cron trigger tutorial for syntax details.