mradder/filament-logger
Community-maintained Filament audit/activity logging built on spatie/laravel-activitylog. Includes a ready-made Activity resource with filters and diffs, CSV/JSON exports, dashboard widgets, and automatic logging for resources, models, auth, notifications, and custom events.
Community-maintained continuation of the original Filament Logger package by Z3d0X.
Filament Logger is an audit log and activity log package for Filament admin panels.
Built on spatie/laravel-activitylog, it adds a ready-made Filament activity resource plus automatic logging for resources, models, auth events, notifications, and custom domain events.

Use it when you need to:
| Package | Version |
|---|---|
| PHP | ^8.2 |
| Filament | ^3.0, ^4.3.1, or ^5.0 |
| Laravel contracts | ^11.0, ^12.0, or ^13.0 |
Filament 4 support starts at 4.3.1 because earlier 4.x releases were affected by an upstream security issue fixed in 4.3.1. See the Filament security advisory and the v4.3.1 release notes.
The package includes compatibility shims for Filament 3.x, 4.x, and 5.x, and the supported range is verified against the CI matrix. If a future Filament release introduces a new breaking API change, a follow-up package update may still be required.
Install the package:
composer require mradder/filament-logger
Publish config and the Spatie activity log migrations:
php artisan filament-logger:install
php artisan migrate
Register the activity resource in your panel provider:
use Filament\Panel;
public function panel(Panel $panel): Panel
{
return $panel
->resources([
config('filament-logger.activity_resource'),
]);
}
In multi-guard applications, you can scope access-event logging to specific guards.
Set access.guards to an allow-list:
'access' => [
// ...
'guards' => ['web'],
],
Behavior:
null (default): log access events from all guards (backward compatible behavior)['web'] (or any list): for events that include a guard property (Login, Logout, Failed), only the listed guards are loggedguard property (Lockout, PasswordReset, and optional Fortify recovery-code events) continue to be loggedExample for a Filament panel + storefront app:
'access' => [
// Log only panel auth events from the web guard.
'guards' => ['web'],
],
See CHANGELOG for recent changes.
See CONTRIBUTING.md for contribution guidelines and CODE_OF_CONDUCT.md for community expectations.
Please review our security policy for responsible disclosure details.
The MIT License (MIT). See LICENSE.md for details.
How can I help you explore Laravel packages today?