Logbook: Usage, archiving, and restoration

The logbook records all changes to objects and categories in i-doit. It serves as an audit trail and is relevant for compliance requirements (e.g. BSI OPS 1.1.5).

Viewing the logbook

The logbook is accessible via Extras > Logbook. Entries can be filtered by time period, user, object type, and change type.

Each object also has its own logbook in the Logbook category.

Archiving the logbook

For large installations, the logbook can significantly increase the database size and impact performance (especially during updates). Archiving moves old entries to a separate database.

Configuring archiving

The configuration is located under Extras > Logbook > Archive.

Running the archive

sudo -u www-data php console.php logbook:archive \
    --user admin --password admin --tenantId 1

Prerequisites:

• An empty target database must exist
• A database user with permissions on this database
• Database connection details entered in the archive configuration

Restoring the logbook

Archived logbook entries can be restored on request. Contact support at help@i-doit.com with the archived database details.

Extended logbook configuration

Under Extras > Logbook > Logbook Configuration, extended logbook settings can be configured.

Tips

• Set up regular archiving via cronjob
• Archive the logbook before i-doit updates — large logbook tables significantly slow down migrations
• Regularly back up the archive database

Detailed documentation: Logbook in the Knowledge Base