Filament Logger Laravel Package

Product Decisions This Supports

• Build vs. buy for admin audit trails. This package supplies a Filament-native viewer for model activity logs (typically backed by spatie/laravel-activitylog). It answers a recurring "do we build our own change history UI?" question with a cheap, maintained default — freeing engineering time for differentiated work.
• Compliance and accountability roadmap. Supports decisions around audit logging for admin-facing changes: who changed what, when, and from where. Relevant if your roadmap includes SOC 2-style controls, internal access reviews, or customer-facing "activity history" features.
• Admin UX investment. Rather than exposing raw database rows, this gives operations/support teams a searchable, filterable record of changes inside the Filament panel — reducing support escalations and engineering interrupts ("why did this record change?").
• Platform standardization. v0.8.0's Laravel 12 compatibility is a concrete signal for the framework-upgrade decision: this dependency will not block a Laravel 12 migration, which de-risks the upgrade timeline.
• Localization coverage. The new Armenian translation is minor on its own, but it evidences an actively localized package — relevant if you serve non-English admin users and are deciding whether to depend on community translations or patch them in-house.

When to Consider This Package

Consider adoption when all of the following hold:

• You run a Filament admin panel and already use (or are willing to adopt) spatie/laravel-activitylog for the underlying log storage — this package is a UI layer, not a logging engine.
• You need an out-of-the-box audit/history screen for admins, not a bespoke analytics product.
• You are on, or planning, Laravel 11/12 — v0.8.0 explicitly adds Laravel 12 compatibility, so the upgrade path is clear.
• Your team accepts a 0.x dependency and the associated semver looseness; pin versions and review changelogs on upgrade.

Look elsewhere when:

• You need immutable, tamper-evident audit logs (append-only storage, signing, external SIEM export) — this is an admin convenience tool, not a compliance-grade ledger.
• You are not on Filament, or you need logging for high-volume, request-level telemetry rather than model change tracking.
• You require a stable 1.0+ public API with long-term support guarantees; the pre-1.0 version number implies possible breaking changes between minor releases.
• You need first-class enterprise support or SLAs — this is a community package with single-maintainer risk (see the "New Contributors" note; bus factor is worth flagging).

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost open-source plugin that gives our admin team a built-in history of every change made in the back office — who changed what and when. It replaces a feature we would otherwise have to design and build ourselves, and the latest release confirms it works with Laravel 12, so it won't hold up our framework upgrade. Cost is effectively zero; the main caveat is that it is a community project at version 0.8, so we should pin the version and treat it as an admin convenience feature rather than a compliance control.

For engineering: Add z3d0x/filament-logger on top of spatie/laravel-activitylog to get a Filament resource for browsing activity records. v0.8.0 is essentially maintenance: a Dependabot bump, an Armenian locale addition, and — the substantive item — Laravel 12 compatibility. No new features and no documented breaking changes in this release. Constraints to note: it is pre-1.0 (pin exact versions and read changelogs before minor bumps), it is a presentation layer over the activity log so logging configuration, retention, and pruning remain our responsibility, and the project has a small contributor base, so we should be prepared to vendor or fork it if maintenance stalls. Recommendation: adopt for the admin panel, keep it out of any compliance-critical audit path unless we add hardening (retention policy, restricted DB access, export to immutable storage).