This module enhances Drupal's database logging by allowing you to set time limits for log entries instead of a fixed quantity. It adds a timestamp index for better performance and lets you configure different retention periods for various log types. This helps manage database size while retaining logs for a specified duration.
This module is useful for projects where you wish to keep database logging messages for a set period of time. You understand the risks that setting a time limit increases the risk of having a high quantity of items in your database log.
Features
This enhances the Database Logging Module from core by:
- Adding an index on the timestamp for performance filtering by date (eg, you can use this in the /admin/reports/dblog View)
- Providing an option to have cron delete messages by amount of time that has passed rather than by quantity of messages
- Control the amount of time per module, e.g. keeping login logs for a month, but cron logs for just a week
Post-Installation
Go to /admin/config/development/logging and choose 'Timespan' instead of the default 'Row limit'. Enter a timespan like '-7 days' to delete messages that are older than 7 days. This accepts anything that strtotime() accepts.
Ask your assistant about Database Logging Time
Check compatibility with your Drupal and PHP version, maintenance and security coverage, from current release data. How it works
Depends on
Dependencies of the latest stable release
- dblog Drupal core
Required by
Tracked projects that depend on this one
No tracked projects depend on this one yet.