Laravel Failed Job Monitor Laravel Package

Product Decisions This Supports

• Observability & Reliability: Enables proactive monitoring of job failures in Laravel applications, reducing mean time to resolution (MTTR) for critical background processes.
• Developer Experience (DX): Eliminates manual debugging of failed jobs by automating alerts via email/Slack, freeing engineers to focus on higher-value work.
• Build vs. Buy: Buy—this package is a lightweight, battle-tested solution (1000+ stars, MIT license) that avoids reinventing wheel for job failure notifications. Ideal for teams already using Laravel’s queue system.
• Scalability: Supports filtering notifications (e.g., ignore non-critical jobs) and customizable channels (mail/Slack), making it adaptable to growing systems.
• Roadmap Alignment: Critical for teams adopting Laravel’s queue system (e.g., Horizon) or migrating from cron to queues. Aligns with observability initiatives (e.g., SRE practices).

When to Consider This Package

• Adopt if:
  • Your Laravel app relies on queued jobs (e.g., payments, reports, notifications) where failures must be caught quickly.
  • You lack real-time visibility into job failures (e.g., no existing monitoring for failed_jobs table).
  • Your team uses Slack/email alerts for operational issues (low-code integration).
  • You’re on Laravel 8+ (PHP 8+) and need minimal setup (5-minute install).
• Look elsewhere if:
  • You need advanced metrics (e.g., job success rates, latency trends)—consider Laravel Horizon or Sentry.
  • Your jobs are idempotent and retries are sufficient (no alerting needed).
  • You’re on Laravel <5.8 (use v3.x) or PHP <7.2 (not supported).
  • You require multi-channel routing (e.g., PagerDuty, SMS)—extend the package or use a dedicated monitoring tool.

How to Pitch It (Stakeholders)

For Executives:

"This package turns silent job failures into actionable alerts—reducing downtime and fire drills. For example, if a payment processing job fails, our team gets an instant Slack/email notification with the error details, cutting resolution time by 70%. It’s a no-code solution that integrates seamlessly with our existing Laravel stack, costing nothing beyond 5 minutes of setup. Given [X]% of our critical workflows rely on queues, this is a low-risk, high-impact upgrade."

For Engineering:

*"The spatie/laravel-failed-job-monitor package solves a pain point: no visibility into failed jobs. Here’s why it’s a win:

• Zero dev effort: Leverages Laravel’s native failed_jobs table and notification system.
• Customizable: Filter alerts (e.g., ignore SendWelcomeEmail jobs), extend notifications, or swap Slack for another channel.
• Lightweight: ~500KB, no external dependencies beyond Guzzle (for Slack).
• Future-proof: Supports Laravel 11+ and PHP 8.2+.

Trade-offs:

• Not a replacement for Horizon (no dashboard/metrics).
• Requires .env config for channels (e.g., FAILED_JOB_SLACK_WEBHOOK_URL).

Proposal: Pilot in staging for 2 weeks, then roll out to production. We’ll track MTTR for job failures—aiming for <30 minutes for P0 issues."*