Data clean up
Data retention policies are adjusted by first creating data_retentions.xml
in path/to/jadu/config
if it does not already exist.
The syntax of adding a new policy to data_retentions.xml
is
<item key="{{ key }}">{{ value }}</item>
The example below deletes all completed queue job after 48 hours:
<data_retentions config:type="array">
<item key="completed_queue_jobs">48</item>
</data_retentions>
Once the changes are made to data_retentions.xml, clear the config cache.
List of Data retention policies
Title | Key | Unit | Default Value | Description |
---|---|---|---|---|
Queue Jobs | completed_queue_jobs | hours | 24 | Queue items that have been successfully processed are retained for a period of time to allow investigation of faults and confirmation of completion. By default, completed jobs are retained for 24 hours after their completion time before being deleted on the next run of the queue. |
User Login | supported_user_login_period | hours | 8760 | All successful login are logged in a table and are retained for a period of time to allow the audit. By default, successful logins are retained for 8460 hours (1 year) after their login time before being deleted on any next successful login by any user. |
User Failed Login | supported_failed_user_login_period | hours | 8760 | All failed login are logged in a table and are retained for a period of time to allow the audit. By default, all failed logins are retained for 8460 hours (1 year) before being deleted on next failed login try by any user. |