Weave Code
Action Logger Laravel Package
laravel-enso/action-logger
Laravel Enso Action Logger provides an audit trail for user actions, recording who did what and when so you can track changes and activity across your application.
Laravel Enso logger for users' actions so you can keep track of who did what
Frequently asked questions about Action Logger
- What is laravel-enso/action-logger used for?
- It is Laravel Enso's logger for user actions, designed to keep an audit trail of who did what and when across an Enso application. It is a component of the Enso admin scaffold, not a general-purpose audit package for any Laravel app.
- Can I use laravel-enso/action-logger outside Laravel Enso?
- It is not recommended for a standalone Laravel application because it assumes Enso's application structure, user model, and conventions for models, migrations, and service providers. Using it outside Enso creates an implicit dependency on the broader ecosystem. For non-Enso Laravel apps, compare spatie/laravel-activitylog or owen-it/laravel-auditing.
- How do I install laravel-enso/action-logger?
- Install it with Composer using composer require laravel-enso/action-logger inside an existing Laravel Enso codebase, then publish and run the package migrations if the README requires it. Confirm the service provider is registered or auto-discovered, and verify that the models you care about emit the events the logger subscribes to. Expect to add glue code for domain-specific actions beyond standard CRUD.
- Which Laravel and PHP versions does laravel-enso/action-logger support?
- The package is part of Laravel Enso and versions in lockstep with Enso core, so check its composer.json and README for the supported Laravel and PHP matrix rather than assuming broad compatibility. Pin both the package and Enso core to tested versions in composer.json. Treat Laravel or Enso upgrades as a coordinated platform bump, not an isolated package update.
- Does laravel-enso/action-logger record who did what and when?
- Yes, its purpose is to record user actions so you can track who did what and when in an Enso application. Before relying on it for compliance, verify the actual schema and event coverage against your requirements, including whether it captures actor, action, target, timestamp, IP, and before/after payload if you need those fields. Do not assume those fields exist without checking the migrations and logged data.
- Can I log custom actions beyond standard CRUD with laravel-enso/action-logger?
- The package's built-in hooks are centered on Enso conventions and Eloquent operations, so expect to write glue code for domain-specific actions that are not simple CRUD. Map your domain events to the package's action vocabulary and confirm the model events you need are actually subscribed. Test custom action logging explicitly before go-live.
- How should I configure retention and indexing for the action log table?
- Define retention, indexing, and access controls for the action log table before production, because audit data grows quickly and compliance queries need predictable performance. Index the columns your team queries most, typically actor, action, target, and timestamp, based on the package schema. If you cut over from a legacy audit store, keep the old store read-only afterward and plan a cutover date.
- How do I test that laravel-enso/action-logger is capturing actions?
- Stand up an Enso baseline in a non-production environment, enable action logging, instrument the model and event set, perform representative actions, and assert that the expected rows are written. Include custom domain actions and negative cases where logging should not occur. Use a test database with the package migrations applied so the assertions match production schema.
- What are the best alternatives to laravel-enso/action-logger for Laravel audit logging?
- For general Laravel audit logging, spatie/laravel-activitylog and owen-it/laravel-auditing are more widely adopted, framework-agnostic, and independently maintained. They are the correct comparison set for non-Enso applications. If you have committed to Laravel Enso as a platform, laravel-enso/action-logger can fit as part of that stack.
- Is laravel-enso/action-logger actively maintained and safe for production?
- Treat it cautiously: the package has a very small user base, weak community signals, and a single-ecosystem dependency chain, so abandonment or slow Laravel/Enso version bumps are realistic risks. There is also lock-in to Enso's data model for audit history and transitive breakage when upstream Enso packages change. Use it only if Enso is already a committed platform decision, pin tested versions, and do not make it your audit backbone while Enso adoption is undecided.
Weaver
How can I help you explore Laravel packages today?