- What does stephenjude/filament-debugger do?
- It is a Filament plugin that surfaces Laravel Telescope, Horizon, and Laravel Pulse inside an existing Filament admin panel. It lets developers inspect logs, errors, queues, and diagnostics without leaving the dashboard. It is intended for local and staging workflows rather than as a core application dependency.
- How do I install filament-debugger in Laravel?
- Install it via Composer and register the plugin on a Filament panel. You also need the underlying Telescope, Horizon, or Pulse packages installed and configured for the tools you want to expose. Publish and configure any package assets as needed, then verify routes and access in a non-production environment.
- Which Laravel and Filament versions are supported?
- Compatibility should be confirmed against the package composer.json and release history before adoption. Because it is a wrapper around Filament and the observability tools, most breakage comes from upstream Filament or Telescope, Horizon, and Pulse updates. Pin the package version and test upgrades in staging.
- Does filament-debugger embed Telescope and Horizon or just link to them?
- The package is described as surfacing Telescope, Horizon, and Pulse inside the Filament admin panel, but the exact embedding versus linking behavior should be validated in a proof of concept. Check whether each tool full UI is rendered in-panel or exposed via navigation links. This matters for authorization and route-level access control.
- Is filament-debugger safe to use in production?
- It is best scoped to local and staging environments or a tightly authorized production admin panel. The underlying tools can expose sensitive request, job, queue, and application data, so misconfiguration could create access-control or data-exposure risk. Use explicit environment checks and authorization gates before enabling it outside local development.
- How do I restrict access to the debugger in Filament?
- Apply authorization at both the Filament panel and route level, not just by hiding navigation items. Use Laravel gates or policies and environment checks to limit who can reach the debugger pages. If the plugin does not enforce every guard itself, wrap or conditionally register it in non-production environments.
- Does filament-debugger work with multiple Filament panels or tenancy?
- The package is registered per Filament panel, so you can limit it to a dedicated operations or platform panel. Support for multi-tenant panels is not clearly documented and should be tested against your tenancy setup. Validate that tenant scoping and authorization behave correctly before enabling it broadly.
- Are Telescope, Horizon, and Pulse all required by filament-debugger?
- The package is designed around those observability tools, but it is unclear whether each one is optional individually. In practice, install and configure only the tools you actually use and verify the plugin behavior when one is absent. Confirm this in a local proof of concept before standardizing.
- What are alternatives to filament-debugger?
- You can access Laravel Telescope, Horizon, and Pulse through their native dashboards or CLI commands without a Filament wrapper. Teams may also build custom Filament pages or navigation links to those tools. Filament Debugger is mainly useful when you want to consolidate existing observability tools into one admin surface.
- How is filament-debugger maintained and what happens on Filament upgrades?
- It appears to be a small, low-adoption package with likely single-maintainer support, so compatibility with future Filament releases is not guaranteed. Assign ownership for upgrade checks around Filament major releases and review the package quarterly. Pin the version in Composer and keep a fallback path to direct tool URLs or CLI access.