- What is z3d0x/filament-logger used for?
- It adds activity logging to Filament admin panels. It records model and authentication events and provides a browsable Filament resource for reviewing logs. It is designed for Laravel applications already using Filament that need operational visibility into model or admin actions.
- Does filament-logger support Laravel 12 and earlier Laravel versions?
- Version 0.8.0 adds Laravel 12 compatibility, which removes a major adoption blocker for teams on Laravel 12. For Laravel 11 or earlier, v0.8.0 may be optional unless you need its dependency updates or translation additions. Confirm the exact Laravel, Filament, PHP, and database constraints before upgrading or installing.
- How do I install filament-logger in a Laravel Filament app?
- Install the package with Composer, register the plugin in a Filament panel provider, publish or configure the package settings, and run any package migrations. Then verify that model and authentication events are captured and that the log resource appears in the panel. Configure retention and sensitive-data handling before enabling broad logging in production.
- Which events and models does filament-logger log by default?
- The package records model and authentication events and supports configurable models and events. The available assessment does not list the complete default model and event set, so review the published configuration after installation. Adjust the configuration to match only the models and events you actually need.
- Is filament-logger suitable for compliance-grade audit logging?
- It is not sufficient by itself for strict compliance-grade audit requirements. The assessment notes that compliance use needs additional controls for immutability, retention, access, and PII handling. Use it primarily for operational visibility unless you add those controls around it.
- Can I customize which models and events filament-logger logs?
- Yes, the package is described as configurable for models, events, and permissions. Publish the configuration and review defaults before enabling it broadly. Limiting logging to relevant models and events helps control log volume and sensitive data capture.
- Is z3d0x/filament-logger actively maintained?
- It is a community-maintained package with active dependency updates, including Laravel 12 compatibility in v0.8.0. Because it is pre-1.0, minor releases should be reviewed rather than automatically merged. No commercial SLA is evident, so support depends on GitHub issues and community response.
- How should I handle log volume and retention with filament-logger?
- Activity logs grow with application usage, so plan for database indexing, retention or purge jobs, archival, and monitoring of table growth. Configure retention before production use and review high-write paths if logging is synchronous. Avoid logging unnecessary events or sensitive payloads.
- Is v0.8.0 a drop-in upgrade from v0.7.3?
- The release assessment expects a Composer version bump rather than a data migration, with no stated breaking changes from v0.7.3 to v0.8.0. Still verify published configuration and assets, run any package migrations, and test log capture and Filament UI behavior in staging. Keep a rollback pin to v0.7.3.
- How do I test filament-logger before using it in production?
- Run a short spike or staging deployment covering schema, logging scope, permissions, translations, and PII redaction. Trigger model and authentication events and confirm they appear correctly in the Filament log resource. Also test retention jobs and your rollback path to the previous package version.