Laravel Failed Job Monitor Laravel Package

Product Decisions This Supports

• Observability & Reliability Roadmap: Integrate proactive monitoring for job failures to reduce MTTR (Mean Time to Recovery) and improve system resilience. This aligns with initiatives to enhance DevOps practices and automate incident response.
• Build vs. Buy: Buy—this package eliminates the need to build custom job failure monitoring from scratch, saving engineering time while leveraging battle-tested, community-supported code.
• Use Cases:
  • Production Monitoring: Alert engineers immediately when critical background jobs (e.g., payment processing, data syncs) fail, reducing downtime.
  • Queue Health Dashboard: Supplement existing monitoring tools (e.g., Laravel Horizon) with actionable notifications for failed jobs.
  • Multi-Environment Support: Configure different notification channels (e.g., Slack for production, email for staging) via environment-specific configs.
  • Custom Workflows: Extend the default notification logic to trigger escalation policies (e.g., PagerDuty alerts for repeated failures) or log failures to a SIEM system.

When to Consider This Package

• Adopt if:

  • Your application relies on queued jobs for critical business logic (e.g., payments, notifications, data pipelines).
  • You lack real-time visibility into job failures in your current monitoring stack (e.g., no alerts for failed jobs in Horizon or Sentry).
  • You want to reduce alert fatigue by filtering notifications (e.g., only alert for jobs with priority: high).
  • Your team uses Laravel’s native notification system (e.g., already configured Mail/Slack channels).
  • You’re on Laravel 8+ and PHP 8+ (or willing to upgrade).

• Look elsewhere if:

  • You need advanced job retry logic (consider spatie/laravel-backup or custom retry queues).
  • Your stack doesn’t use Laravel (e.g., Symfony, Node.js)—opt for platform-native solutions.
  • You require detailed job execution metrics (e.g., duration, memory usage)—combine with Laravel Horizon or Prometheus.
  • You’re on Laravel <5.8 or PHP <7.2 (package dropped support for these versions).
  • You need multi-channel notifications beyond Mail/Slack (e.g., SMS, Teams)—extend the package or use a dedicated alerting tool like PagerDuty.

How to Pitch It (Stakeholders)

For Executives:

"This package turns silent job failures into actionable alerts, reducing downtime and improving system reliability. For example, if a payment processing job fails in production, our team gets notified instantly via Slack or email—cutting recovery time by 50%. It’s a low-effort, high-impact way to monitor our queue health without building custom infrastructure. The cost? Zero—it’s open-source and integrates seamlessly with our existing Laravel setup."

Key Outcomes:

• Faster incident response: Alerts delivered in real-time to the right teams.
• Reduced operational risk: No more "we didn’t know the job failed" surprises.
• Scalable: Works for both small teams and high-volume queues.

For Engineering/DevOps:

*"This package solves a common pain point: how to reliably detect and alert on failed queued jobs without reinventing the wheel. Here’s why it’s a no-brainer:

• Zero setup for basic use: Just configure your Slack/Mail channels, and you’re done.
• Extensible: Need custom logic? Override the notification class or filter failures (e.g., ignore SendWelcomeEmail jobs).
• Leverages Laravel’s ecosystem: Uses the built-in notification system, so you’re not locked into proprietary tools.
• Lightweight: No heavy dependencies—just 10KB of code.

Proposal:

1. Phase 1: Enable Slack alerts for all failed jobs in production (1 hour).
2. Phase 2: Add filtering to exclude low-priority jobs (e.g., priority: low) and integrate with our existing PagerDuty rules.
3. Phase 3: Extend to staging with email alerts for critical paths.

Alternatives considered:

• Custom solution: Would take 2–3 dev days to build and maintain.
• Third-party tools: Tools like Sentry or Datadog offer job monitoring but add complexity and cost.

This package gives us 90% of the value with 10% of the effort."*