- What is mradder/filament-logger used for in Laravel?
- Filament Logger is an audit and activity log package for Filament admin panels built on spatie/laravel-activitylog. It gives you a ready-made activity review resource with filters, diffs, saved tabs, date presets, CSV and JSON exports, dashboard widgets, alerts, and automatic logging for resources, models, auth events, notifications, and custom events. It is best treated as a Filament panel feature for reviewing admin activity and security events, not as a standalone audit platform.
- How do I install Filament Logger in a Laravel Filament panel?
- Run composer require mradder/filament-logger, then run php artisan filament-logger:install to publish the config and Spatie migrations. Run php artisan migrate, then register config('filament-logger.activity_resource') in your panel provider's resources array. After that, configure authorization and guard scoping before exposing the resource to panel users.
- Which Laravel and Filament versions does filament-logger support?
- The documented compatibility surface is PHP ^8.2, Filament ^3.0 or ^4.3.1 or ^5.0, and Laravel contracts ^11 or ^12 or ^13. The Filament 4 floor of 4.3.1 is deliberate and tied to an upstream Filament security advisory. Because the package includes compatibility shims, verify your exact Filament patch version and expect to track Filament's upgrade cadence.
- Why is my Filament Logger activity resource locked or returning 403?
- Since 0.9.0 the activity resource is strict by default and requires an explicit Activity policy. If you register the resource without a policy, the screen can be locked out or broken for panel users. Do not solve this by disabling strict authorization, because that exposes the full audit trail, including actor identities and before-and-after diffs, to every panel user.
- How do I configure access.guards to avoid logging customer auth events?
- In apps with a Filament admin panel plus a separate storefront or customer guard, set the access.guards allow-list to only the guards whose events belong in the admin audit stream. The default is null, which logs all guards and can write customer authentication events into the admin log. That inflates volume and pollutes the review UI, so guard scoping should be an explicit setup ticket.
- Does Filament Logger provide compliance-grade audit trails for SOC 2 or HIPAA?
- No, it should not be treated as a control-grade audit trail for SOC 2, HIPAA, or PCI. Activity rows are ordinary mutable database rows in your primary application database, with no hash chaining, append-only guarantee, external sink, or WORM storage. Framing this package as a compliance audit control is a mis-scoping risk rather than a missing feature.
- Can I export Filament Logger audit data to CSV or JSON?
- Yes, Filament Logger provides CSV and JSON exports for filtered audit data. Exports are intended for compliance support, incident response, and review workflows, but you still need to control who can access them. Review export permissions alongside the Activity policy because exported diffs and actor identities are sensitive.
- How does Filament Logger log models, resources, auth events, and custom events?
- It builds on spatie/laravel-activitylog and adds observers for model and resource lifecycle events, including create, update, delete, restore, force-delete, and replicate. It also supports auth events, notifications, and a custom domain event API so you can log application-specific actions without building your own audit UI. Be aware that observers on hot models can cause write amplification.
- Is Filament Logger safe for production and actively maintained?
- It can be viable in production for Filament panel activity review if you configure the Activity policy, guard allow-list, and export access correctly. The maintenance risk is real: it is a community-maintained continuation by a single author, with very thin adoption evidence such as 26 stars and 0 Packagist dependents. The project has CI, PHPStan, docs, and quality-gate workflows, but you should pin versions, verify the latest release on Packagist, and plan an exit path to the underlying Spatie data.
- What are alternatives to Filament Logger for Laravel audit logging?
- The closest alternative is using spatie/laravel-activitylog directly and building your own Filament activity resource, filters, exports, and widgets. That costs more UI work but keeps the integration fully under your control. If you need compliance-grade tamper evidence, choose a dedicated audit platform with append-only or external immutable storage instead of a primary-database activity log.