Log Entity Operations

Synopsis

Drupal by defaults adds a log message for entity operations when done from
interface. We miss these entries in logs when operations are performed through
code.

With data coming from remote systems or after complex operations performed in
your code, tracking changes on entities is impossible, as no log entries are
written. Most of the time, revisions are also disabled for custom entities to
prevent excessive storage usage.

This project aims to add log entries for all operations performed on entities
of the selected entity bundles. Whenever you want to track operations that are
performed on an entity, you can enable logging of all changes that are being
made. This helps you to get an overview on which changes are performed on your
entities.

Example

If you're running an e-commerce site, you might synchronize your products
through an API. You do not want to enable revisions as you already have
revisions of your products in your external system - but you want to check
on which changes have been made on your products - and if the synchronization
still works as desired.

Detailed Entity Logging

The submodule "Log Entity Operations to custom Entities" provides even more
comfort by providing a filterable overview over all logs made by this module.
This can help you tracking down changes when dealing, for example, with
missing data, where revisions are no longer available. You will find the
corresponding log entries on the given entity which also gives you the
information about which user deleted it and when.

Installation

Install as you would normally install a contributed Drupal module. If you want to use the dedicated log overview, also install the submodule "Log Entity Operations to custom Entities".

Configuration

Visit /admin/config/development/log-entity-operations to configure the module.