Weave Code
Actionlogger Laravel Package
laravel-enso/actionlogger
Laravel Enso Action Logger provides an audit trail for your application by recording user actions and model changes. It captures who did what and when, with configurable logging and an easy way to review activity.
Laravel Enso logger for users' actions so you can keep track of who did what
Frequently asked questions about Actionlogger
- What does laravel-enso/actionlogger do?
- Laravel Enso Action Logger is a satellite module for Laravel Enso that records user actions so administrators can see who did what and when. It typically stores records in an Eloquent-backed action_logs table and includes Enso plumbing such as a service provider, migrations, config, and a UI listing in the admin panel. It is an activity feed for Enso applications, not a general-purpose auditing library.
- Can I use laravel-enso/actionlogger in a non-Enso Laravel app?
- No, it is designed as a first-class citizen of an Enso application and assumes Enso's user model, auth guard, migration conventions, and menu and permission registration. Outside Enso you would be porting rather than integrating, and the same capability is better served by framework-agnostic packages such as spatie/laravel-activitylog or owen-it/laravel-auditing.
- How do I install laravel-enso/actionlogger in an existing Enso app?
- In an existing Enso app, install it with Composer, run the package migrations, apply the provided trait to the models you want to log, seed the relevant permissions, and verify the Enso UI listing. The package install is usually low effort, but defining which models and verbs matter, redacting PII, and planning retention is the larger governance task.
- Which Laravel versions does laravel-enso/actionlogger support?
- The package tracks Enso major releases, and Enso itself tracks Laravel majors, so support depends on the matching Enso release. Check the package's composer.json constraints and Enso release notes before upgrading Laravel or Enso, because you may need to upgrade this package in lockstep. A lagging release can block a platform upgrade.
- Is laravel-enso/actionlogger a compliance-grade audit trail?
- No. The described scope is an activity feed that records the acting user, target record, action verb, and timestamp; nothing indicates append-only or tamper-evident storage, actor identity that survives user deletion, request correlation IDs, or retention policy. Treating it as a regulatory audit trail would be an architecture error. Use a purpose-built compliance solution if you need evidentiary guarantees.
- Does laravel-enso/actionlogger capture before and after model values?
- The description points to capturing the action verb, the target model or record, the acting user, and a timestamp; before and after value diffs are not indicated. Diff capture materially changes storage volume and PII exposure, so verify in the source or documentation whether your version stores payloads. If you need value-level auditing, confirm this before committing.
- Is action logging in laravel-enso/actionlogger synchronous or queued?
- The package description does not specify whether log writes are synchronous or queueable. If synchronous, every instrumented action adds an INSERT on the request path and a logging failure may fail the user action; if queued, you inherit queue lag and silent-drop risk. Review the implementation and decide whether audit writes should share the business transaction.
- How should I handle PII and retention with laravel-enso/actionlogger?
- Captured payloads can contain emails, names, addresses, or free text, so without explicit redaction the action_logs table becomes a shadow copy of production data outside normal retention and access controls. Define a redaction policy, restrict access, and wire archival or pruning jobs. Also confirm what the package actually stores before assuming it is safe for your data classification.
- How do I test laravel-enso/actionlogger in my Laravel test suite?
- Use Enso's testing conventions and assert that expected rows land in the action_logs table after the action under test. You will typically need an authenticated Enso user and the relevant model trait applied, and you should cover both success and failure paths for the logging write. Check the package source for any test helpers or configuration overrides.
- What are the alternatives to laravel-enso/actionlogger, and is it production-ready?
- For non-Enso Laravel apps, spatie/laravel-activitylog and owen-it/laravel-auditing are the mainstream alternatives with broader adoption and better documentation. For Enso shops, this package is the low-ceremony fit, but adoption signals are weak: it is a single-maintainer, ecosystem-internal package with little external validation. Assess production risk, version lock-in, and Enso's own release cadence before relying on it.
Weaver
How can I help you explore Laravel packages today?