- How do I install Filament Logs Explorer in a Laravel app?
- Install it with composer require laboiteacode/filament-logs-explorer, then register the plugin in your Filament panel provider. You can publish and adjust the config file or use the fluent per-panel API for navigation and authorization options. A Filament-fluent developer can typically complete the setup in under an hour.
- Which Laravel, PHP, and Filament versions does filament-logs-explorer support?
- The package supports PHP 8.2 through 8.5, Laravel 12 and 13, and Filament 4 and 5. Check the compatibility table in the README before upgrading a production panel. It is a Filament plugin, so it does not target older Filament versions.
- How does Filament Logs Explorer find and group my Laravel log files?
- It resolves log paths from config/logging.php rather than using a hardcoded path. Single, daily, and monolog stream handlers are supported, along with the file-based members of a stack channel. Files are then grouped by logging channel in the Filament page.
- Can I configure the navigation group, sort order, or cluster per Filament panel?
- Yes. Navigation group, sort order, cluster, and related placement options can be set in the published config file or through the fluent per-panel plugin API. Because panel context is resolved at plugin registration time, changes to placement are evaluated early. If you cache Filament components, re-run php artisan filament:optimize after changing them.
- Is it safe to open very large Laravel log files in the browser?
- Files above a configurable size are truncated, and the viewer loads the end of the file first so recent entries appear immediately. That avoids dumping an entire very large daily log into the slide-over. You should still validate your truncation limit against a realistic staging log corpus before relying on it in production.
- How do I restrict who can access the logs explorer?
- Access is controlled by a canAccess() hook that drives both the navigation item and the route. You should wire it to an explicit gate or policy rather than assuming every panel user should read logs. Log files often contain credentials, tokens, PII, and stack traces, so review path resolution and authorization during a staging spike.
- Can users delete log files from the Filament panel?
- Yes. A log file can be deleted from the list or from the slide-over viewer after a confirmation dialog. Deletion uses its own authorization hook, independent of read access. That lets you allow viewing logs while restricting destructive actions to a smaller group.
- Does Filament Logs Explorer work with multiple Filament panels?
- It can be used in multi-panel Filament installations. Version 1.0.2 fixes a bug where the page could pick up the cluster configured on another panel. Other placement options such as navigationGroup, navigationSort, and slug should still be checked in a multi-panel setup. Re-run filament:optimize after upgrades so cached registrations do not point at stale placement.
- Do I need to run php artisan filament:optimize after installing or upgrading?
- Yes, if your deployment caches Filament components. The cache can hold the old plugin registration, so a deploy that skips filament:optimize may silently show the page in the wrong place or with stale settings. Add the command to your deploy checklist after installation and after every package upgrade.
- Is Filament Logs Explorer compatible with Nova, Backpack, or a custom Blade admin panel?
- No. Filament Logs Explorer is a presentation-layer plugin for Filament panels and is not designed for Nova, Backpack, or a custom Blade admin. If your admin surface is not Filament, the package is not usable without a rewrite.