Filament Jobs Monitor Laravel Package

Product Decisions This Supports

• Observability & Debugging: Enables real-time monitoring of background jobs (e.g., Laravel queues) directly within Filament’s admin panel, reducing reliance on external tools like Horizon or manual logging.
• Multi-Tenancy Support: Critical for SaaS platforms needing tenant-isolated job tracking (e.g., tenant_id filtering, UUID compatibility).
• Developer Productivity: Accelerates debugging by providing a UI for job statuses (failed/pending/success), payload inspection, and bulk actions (e.g., requeueing jobs).
• Roadmap Priorities:
  • Build vs. Buy: Avoids reinventing Horizon-like functionality for Filament users; leverages an MIT-licensed, actively maintained package.
  • Feature Flagging: Configurable via FilamentJobsMonitorPlugin (e.g., navigation visibility, tenant isolation), enabling gradual rollout.
  • Scalability: Supports all queue drivers (database, Redis, etc.) and integrates with Filament Panels for modular deployment.
• Use Cases:
  • SaaS Platforms: Track jobs per tenant without cross-contamination.
  • E-Commerce: Monitor order processing jobs (e.g., UsersCsvExportJob in the example).
  • Legacy Systems: Migrate from Horizon to Filament without rewriting job monitoring logic.

When to Consider This Package

• Adopt When:

  • Your team uses FilamentPHP (v2–v5) and needs Horizon-like job monitoring without vendor lock-in.
  • You require multi-tenancy support (e.g., SaaS) with tenant-aware job filtering.
  • Your queue jobs are critical to business operations (e.g., payments, exports) and need visibility in the admin panel.
  • You prefer open-source over proprietary tools (e.g., Laravel Horizon’s paid tier).
  • Your team lacks bandwidth to build a custom solution but needs real-time job tracking.

• Look Elsewhere If:

  • You’re not using FilamentPHP (this is a Filament-specific package).
  • You need advanced metrics (e.g., job throughput graphs) beyond what this package offers (consider Horizon or custom Laravel monitoring).
  • Your jobs are stateless or don’t require monitoring (e.g., simple CLI tasks).
  • You’re using non-Laravel queue drivers (e.g., RabbitMQ) without Laravel’s queue system.
  • Your team prefers self-hosted solutions over composer packages (e.g., building a custom Filament resource).

How to Pitch It (Stakeholders)

For Executives:

"This package lets us monitor all background jobs (e.g., order processing, exports) directly in our Filament admin panel—like a built-in ‘control tower’ for critical workflows. It’s free, open-source, and integrates seamlessly with our existing SaaS architecture. For example, if a tenant reports an export job failed, our team can instantly see the error and payload without digging through logs. It also supports multi-tenancy out of the box, so we won’t need to build this from scratch. The time-to-value is high: install it, configure it, and start debugging jobs in minutes."

Key Outcomes:

• Reduce mean time to resolution (MTTR) for job failures.
• Eliminate dependency on third-party monitoring tools.
• Future-proof for scaling tenants/jobs without custom dev work.

For Engineering Teams:

*"This is a drop-in replacement for Horizon but tailored for Filament. It gives us:

• UI for job management: View, retry, or delete failed jobs with one click.
• Multi-tenancy support: Jobs are automatically filtered by tenant (e.g., tenant_id in payloads), so we don’t need to write custom scopes.
• Extensibility: We can customize the model, add columns, or integrate with our existing Filament panels.
• Lightweight: No heavy dependencies; just a Filament resource and migrations.

Why not build it ourselves?

• Time: This package handles 80% of use cases out of the box (e.g., job tables, tenant isolation).
• Maintenance: The author actively fixes bugs (e.g., recent Filament 5 compatibility patches).
• Community: 274 stars and growing—we’re not alone in needing this.

Proposal:

1. Pilot: Install in staging to test with our UsersCsvExportJob and tenant-aware jobs.
2. Configure: Publish the plugin to our Filament panel and enable navigation for admins.
3. Monitor: Use it to debug the next job failure—compare to our current workflow (e.g., telescope:search or manual log checks).

Risks:

• Minimal (MIT license, active maintenance, Filament-compatible).
• Migration effort: Zero if we’re not using Horizon today; low if we are (just switch the UI)."*

Call to Action: "Let’s demo this in our next standup—it could save us weeks of dev time and make job debugging as easy as clicking a button."