A Laravel package for logging user activities and model events with a simple API.
Laravel Activitylog is a PHP package for Laravel that enables developers to log user activities and model events within their applications. It provides an easy-to-use API for recording custom activities and automatically tracks changes to Eloquent models, storing all data in a dedicated database table for audit and monitoring purposes.
Laravel developers building applications that require user activity tracking, audit trails, or monitoring of model changes, such as admin panels, SaaS platforms, or content management systems.
Developers choose Laravel Activitylog for its simplicity, seamless integration with Laravel's Eloquent ORM, and powerful features like automatic model event logging and rich activity data storage, all without requiring complex setup or custom code.
Log activity inside your Laravel app
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically logs Eloquent model events (create, update, delete) without manual code, as demonstrated in the README where saving a model triggers activity recording with attribute changes.
Captures detailed changes including old and new attributes in a structured `attribute_changes` collection, providing comprehensive audit trails for debugging or compliance.
Offers a clean, chainable interface for manual logging with properties, subjects, and causers, shown in examples like `activity()->performedOn($model)->log()`.
Designed specifically for Laravel with easy Composer installation, automatic service provider registration, and configurable migrations for different ID types like UUIDs.
Relies solely on a database table for logging without built-in support for alternative backends like log files or external services, which limits flexibility for distributed systems.
The default single-table storage can become a bottleneck in high-volume applications, as the README doesn't address partitioning or archiving strategies for large logs.
Lacks frontend components or dashboards for viewing logs, requiring additional development effort to visualize activity data in admin panels or user feeds.