Weave Code
Filament Activitylog Laravel Package
elpandape/filament-activitylog
Filament Activity Log adds a ready-to-use activity log viewer to your Filament admin panel, letting you browse, search, filter, and inspect recorded model changes and user actions. Built for Laravel and Spatie Activitylog, it helps teams audit changes without leaving Filament.
At a glance
Frequently asked questions about Filament Activitylog
- What is elpandape/filament-activitylog used for?
- It adds a ready-to-use activity log viewer inside a Filament admin panel, built on top of Spatie Activitylog. Instead of building custom pages, you can browse, search, filter, and inspect recorded model changes and user actions from the same admin UI your team already uses. It is a presentation layer for entries that Spatie Activitylog has already recorded.
- How do I install elpandape/filament-activitylog in a Laravel Filament app?
- Install it with Composer using composer require elpandape/filament-activitylog, then register the plugin in your Filament panel provider, typically inside the plugins array. You should already have spatie/laravel-activitylog installed and its activity_log migration run, because this package displays those records rather than creating its own logging pipeline. Check the README for any publishable configuration or assets and run the suggested publish command if required.
- Which Laravel and Filament versions does this package support?
- The authoritative version constraints are in the package composer.json, so check those before installing. Filament plugins are tightly coupled to Filament major versions, so do not assume a plugin built for one Filament major will work on another without verification. Confirm your Laravel, Filament, and PHP versions against the declared requirements, and test in a branch before upgrading production.
- Do I need Spatie Activitylog installed separately?
- Yes. This package is a viewer for Spatie Activitylog data, so the underlying spatie/laravel-activitylog package and its activity_log table must already exist in your application. Your models also need to use Spatie's LogsActivity trait or otherwise write activity entries for the viewer to display. Without recorded entries, the Filament page will have nothing to show.
- Can I search and filter activity log entries by user, model, event, or date?
- The package is designed for browsing, searching, and filtering recorded activity entries inside Filament. The exact filter set depends on the package version, but typical use cases include narrowing by causer, subject, event, and timestamp. If you need extra filters, you can usually extend or customize the Filament resource or table rather than modifying vendor code.
- Does filament-activitylog affect application performance in production?
- The viewer is read-only over your activity_log table, so it does not change how entries are written by Spatie Activitylog. Performance depends mainly on table size, pagination, and indexing, so add indexes for the columns you filter on and prune old records according to your retention policy. Avoid loading very large unfiltered result sets in the admin panel.
- How do I control who can view the activity log in Filament?
- Access should be controlled through Filament authorization, such as policies or visibility checks on the resource or page. Activity logs often contain sensitive context, so restrict viewing to trusted admin or audit roles rather than every panel user. Review the package resource and apply your application's normal authorization conventions.
- Can I customize the activity log table columns or views?
- Filament resources are intended to be customized, so you can typically extend the provided resource or page to adjust columns, filters, and actions. If the package supports publishing views or configuration, publish them first and modify the copies rather than editing vendor files. Keep customizations in your application code so Composer updates remain safe.
- How should I test the activity log viewer with Pest or PHPUnit?
- Use your normal Laravel test setup with RefreshDatabase so the activity_log table exists, and create activity entries through Spatie Activitylog in arrange steps. Then use Filament's testing helpers to assert that the page or table shows the expected records. No special test double is usually needed for a read-only viewer, but verify any package-specific configuration against your test environment.
- What are alternatives to filament-activitylog?
- You can build a custom Filament resource over the activity_log table, use another Filament activity log package, or rely on Spatie Activitylog alone with your own reporting. This package is a good fit when you want a ready-made Filament viewer without writing the UI yourself. If you need immutable, audit-grade logs with tamper evidence, consider a dedicated audit or logging service instead.
Weaver
How can I help you explore Laravel packages today?