Logger

• Highlights
• Requirements
• Quick Start
• Documentation
• Filtering By Auth Guard
• Screenshots
• Changelog
• Contributing
• Security
• Credits
• License

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:

• review admin activity and security events inside Filament
• export audit data for compliance, support, or incident response
• trigger alerts for destructive or high-risk actions
• log custom domain events without building your own audit UI

#Highlights

• Ready-made Filament audit log resource with searchable filters, structured diffs, saved review tabs, and date presets
• CSV and JSON exports for filtered audit data
• Dashboard widgets for top users, top events, activity spikes, and high-risk actions
• Resource and model lifecycle logging, including create, update, delete, restore, force-delete, and replicate flows
• Auth event logging for login, logout, failed login, lockout, password reset, and 2FA recovery usage
• Notification logging plus alerting hooks for mail, Slack, and Discord webhooks
• Custom event API for domain-specific audit events
• Sensitive data redaction, anonymized IP logging, and stricter authorization defaults
• Configurable ignored fields per model and per resource
• Built-in pruning command for retention by age and log name

#Requirements

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.

#Quick Start

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'),
        ]);
}

#Documentation

• Documentation Site
• Installation and Setup
• Security and Authorization
• Configuration Guide
• Activity Review UI
• Custom Events and Alerts
• Roadmap

#Filtering By Auth Guard

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 logged
• events without a guard property (Lockout, PasswordReset, and optional Fortify recovery-code events) continue to be logged

Example for a Filament panel + storefront app:

'access' => [
    // Log only panel auth events from the web guard.
    'guards' => ['web'],
],

#Screenshots

#Changelog

See CHANGELOG for recent changes.

#Contributing

See CONTRIBUTING.md for contribution guidelines and CODE_OF_CONDUCT.md for community expectations.

#Security

Please review our security policy for responsible disclosure details.

#Credits

• Ziyaan Hassan - original developer
• Daniel Green
• Spatie Activitylog Contributors
• All Contributors

#License

The MIT License (MIT). See LICENSE.md for details.