Weave Code
Tomato User Activities Module Laravel Package
tomatophp/tomato-user-activities-module
A TomatoPHP module that logs and displays user activities in your Laravel app, giving admins a clear timeline of actions and events for auditing and monitoring.
Advanced logger is a laravel package used to automatically log every request made to you laravel application. Each request is also identified by hash, which can be used in standard log to identify the request.
Frequently asked questions about Tomato User Activities Module
- How do I install the TomatoPHP User Activities module in Laravel?
- Install it with Composer using composer require tomatophp/tomato-user-activities-module, then run your migrations so the activity log table is created. In a TomatoPHP setup, enable the module so its Filament resource appears in the admin panel. Check the repository README for any required service provider or panel registration steps.
- Does this package work with Filament and the TomatoPHP admin panel?
- Yes. The module is built as a TomatoPHP module and ships with a ready-made Filament interface for browsing and filtering user activity records. Once installed and registered, you can view the audit trail directly inside your existing admin panel without building custom screens.
- Which Laravel versions are supported by this module?
- It is designed for the modern Laravel releases used across the TomatoPHP ecosystem. Because support can change between releases, check the composer.json constraints in the repository for the exact Laravel and PHP versions. Confirm compatibility with your Filament version before installing in an existing project.
- How does the request hash identification work?
- Every request handled by your Laravel application is recorded and assigned a unique hash. That hash is stored alongside the standard log entry, so you can correlate a logged request with its related activity record. This makes it easier to trace a specific request when debugging or auditing behavior.
- Can I filter activity logs by user, date, or request in the admin panel?
- Yes. The included Filament interface is intended for browsing and filtering activity records, so you can narrow the audit trail to the entries you care about. Filters help you review who did what and when without querying the database manually.
- Will logging every request slow down my Laravel application?
- The module automatically logs every request, which adds database writes to your request lifecycle. For most applications this overhead is modest, but high-traffic APIs can generate significant log volume. Test in a staging environment and consider retention or pruning policies if write load becomes a concern.
- Is this package suitable for production audit trails?
- It can serve as a practical audit trail because it captures requests automatically and exposes them in a Filament interface. For production, plan for log retention, database growth, and access control on the admin panel. Treat the logs as sensitive data and restrict who can view them.
- Can I customize the activity log model or migration?
- As with most TomatoPHP modules, you can typically publish and adjust configuration or migrations if the package exposes them. You can extend the underlying model to add relationships or scopes for your own reporting needs. Review the repository structure to see which assets are publishable before making changes.
- How do I test that user activity logging works in my Laravel app?
- Write a feature test that performs a request and then asserts the expected activity record exists in the database. You can also assert that the stored request hash matches the one written to your standard logs. Using Laravel's testing helpers keeps these checks fast and repeatable in CI.
- What are the alternatives to this Laravel user activity logging package?
- Popular alternatives include spatie/laravel-activitylog and owen-it/laravel-auditing, which focus on model-level activity and change tracking. This TomatoPHP module differs by automatically logging every request and providing a Filament admin interface. Choose based on whether you need request-level logging with a ready-made panel or model-centric audit trails.
Weaver
How can I help you explore Laravel packages today?