Weave Code
Eagle Eye Filament Laravel Package
dotswan/eagle-eye-filament
Filament plugin integrating Dotswan Eagle Eye, adding a zoomable image viewer field so you can inspect and preview images directly inside Filament forms and admin panels.
At a glance
Frequently asked questions about Eagle Eye Filament
- What does dotswan/eagle-eye-filament actually add to a Filament panel?
- It is the admin presentation layer for Dotswan Eagle Eye, adding KPI dashboards, an activity explorer, event detail and trace views, heatmaps, history screens and dashboard widgets inside Filament. Instead of hand-building custom resources over Eagle Eye's event tables, you register ready-made pages and widgets in a panel provider. It does not replace Eagle Eye itself; it only renders the audit and activity data that Eagle Eye captures.
- How do I install dotswan/eagle-eye-filament in a Laravel application?
- Require both dotswan/eagle-eye and dotswan/eagle-eye-filament at matching beta versions with Composer, pinning the exact versions in composer.json. Run and verify the Eagle Eye migrations, register the plugin in your Filament panel provider, and confirm that Livewire and Filament assets and panel routes resolve correctly. Do the first install in staging so you can validate ingestion, routing and authorization before exposing screens to users.
- Which Laravel and Filament versions does this plugin support?
- The package targets Laravel 12 or 13 with Filament 5.x and Eagle Eye ^1.0@beta, so it is a strict version-matrix dependency. The PHP version and required extensions are declared in the package composer.json and should be checked before you attempt the install. These are forward-looking constraints, so applications on older Laravel or Filament releases will likely be excluded until they upgrade.
- Do I need to install dotswan/eagle-eye separately from the Filament plugin?
- Yes. dotswan/eagle-eye-filament is only a UI layer, so the Eagle Eye audit and activity backend must already be installed, migrated and capturing events. Install and validate Eagle Eye first, including retention and schema behaviour, then add the Filament UI on top. Avoid mixing a stable Eagle Eye release with a beta UI build unless the maintainers explicitly support that combination.
- How are authorization, multi-tenancy and policy-gated field reveal handled?
- Access is expected to flow through your Filament panel authorization and Laravel policies, with policy-gated reveal controlling who can expand sensitive field values in the activity views. You must configure those policies and reveal rules yourself; the package does not infer your tenancy or permission model. Review multi-tenant scoping and reveal behaviour with a security-minded colleague before production, because the UI surfaces audit data that is normally hidden.
- What does Livewire interaction capture record, and is it a privacy concern?
- The plugin exposes Eagle Eye's Livewire interaction capture, which records user interactions in the admin panel and can include payload data depending on configuration. Treat this as a privacy and security review item: confirm what is captured, how personally identifiable information is redacted or excluded, and how long records are retained. Document the outcome of that review before enabling the capture features for real users.
- Will the dashboards, facets and heatmaps perform well with high event volume?
- Performance depends heavily on Eagle Eye's event volume, table indexing, facet cardinality and how trace timelines are queried, so there is no universal answer. Load-test the dashboards, activity explorer, facets, charts and heatmaps against production-like data before rollout. If queries are slow, plan retention or archival policies and avoid exposing high-cardinality facets to broad admin groups.
- Is it safe to run this beta package in production?
- The package is pre-1.0 and the maintainers state the API may change, so treat it as a tracked beta dependency rather than a stable foundation. Pin exact versions, upgrade Eagle Eye and the Filament UI together, and run regression tests against your panels before each bump. A pilot with a small admin group in a non-production environment is the safest way to judge stability for your workload.
- How should I roll this out and keep it maintained?
- Sequence the work: confirm your Filament 5 baseline, install Eagle Eye beta and verify capture, add the Filament UI in staging, complete the security and privacy review, then performance-test with representative event volume before piloting with a small admin group. Keep both packages in lockstep and document pinned versions plus an upgrade cadence. Budget ongoing time for Composer constraint updates, Filament and Livewire compatibility checks, and runbooks for empty dashboards, authorization failures and rollbacks.
- What are the alternatives to dotswan/eagle-eye-filament?
- The main alternative is building your own Filament resources, pages and widgets directly over Eagle Eye's event models, which gives full control over layout, authorization and query tuning. If you are not committed to Eagle Eye as your audit backend, a different activity-log package with its own Filament UI may fit better. The plugin's value is the prebuilt dashboards and exploration views, so weigh that against the risk of a beta dependency in your admin panel.
Weaver
How can I help you explore Laravel packages today?