Settings

This plugin has some extensive settings to control the activity you want recorded. A rule system allows you to ignore some activity based on its type and the type of request (cp, console, site, yaml config)

Logs can be deleted when they become too old, and be deleted along with the user that created them.

You can also turn off the field changes tracking, if you only care about the event that happened but don't need to know what's been changed.

Elements

These settings apply to all content : entries, globals, categories etc

By default the "update slugs and uris", "elements are propagated" and "elements are resaved" logs are ignored which should be what you need in most cases. Turning on those logs can create lots of useless records as they are triggered by the system.

You can turn off the field changes tracking, if you only care about the event that happened but don't need to know what's been changed.

Config

This setting applies to all config models : Volumes, category groups, sections, sites etc

You can turn off the field changes tracking, if you only care about the event that happened but don't need to know what's been changed.

And lastly, you can ignore events when no changes were made, a little warning here :

Changes are based on a list of fields that the system can track for each entity. Some entities (like a non-native field) may not supported at the moment. So if you change a field's config that is not tracked by the system, a record won't be created when you save it as the system will not calculate changes for it.

Settings

These settings apply to some Control panel settings : General, Emails, Users and Assets.

You can turn off the field changes tracking, if you only care about the event that happened but don't need to know what's been changed.