Laravel Failed Job Monitor
A Laravel package that sends notifications when queued jobs fail, supporting email and Slack out of the box.
What is Laravel Failed Job Monitor?
Laravel Failed Job Monitor is a Laravel package that automatically sends notifications when queued jobs fail. It solves the problem of silent job failures in background processing by alerting developers via email or Slack. The package integrates directly with Laravel's notification system for seamless setup and customization.
Laravel developers who use queue systems for background job processing and need reliable failure monitoring. It's particularly valuable for teams running production applications where job failures could impact business processes.
Developers choose this package because it provides a simple, Laravel-native solution for job failure monitoring with zero custom infrastructure. It's maintained by Spatie (known for quality Laravel packages), supports multiple notification channels out of the box, and offers extensive customization options while following Laravel conventions.
Overview
Get notified when a queued job fails
Use Cases
Best For
- Monitoring failed queue jobs in Laravel applications
- Receiving instant Slack alerts when background jobs fail
- Setting up email notifications for job failures without custom code
- Filtering which job failures trigger notifications
- Customizing notification content and delivery methods
- Integrating job failure alerts into existing Laravel notification workflows
Not Ideal For
- Applications with high-frequency job failures where notification spam would be problematic
- Teams needing a centralized dashboard or historical analytics for failed jobs
- Projects not using Laravel's built-in queue system or notification infrastructure
Pros & Cons
Pros
Monitors Laravel's queue system and triggers notifications immediately when a job fails, as per the package's core feature described in the key features.
Supports email and Slack out of the box, with an extensible architecture for adding custom channels, detailed in the README's installation and configuration sections.
Allows creation of custom notification classes and filter callbacks to tailor alerts, shown in the configuration examples for notification and notifiable customization.
Leverages Laravel's native notification system for compatibility and familiar setup, emphasized in the philosophy and integration notes.
Cons
Using closure-based filters can cause serialization errors when caching configuration, as explicitly warned in the README's notification filtering section, requiring workarounds with separate classes.
Only email and Slack are supported natively; other notification channels like SMS or database require custom implementation, increasing development overhead as noted in the customization options.
Provides only notifications without a visual interface for monitoring or analyzing failures, limiting insight without additional tools like Laravel Horizon or custom logging.
Frequently Asked Questions
Related Projects
LiveWireA full-stack framework for Laravel that takes the pain out of building dynamic UIs.
Debug BarDebugbar for Laravel (Integrates PHP Debug Bar)
IDE HelperIDE Helper for Laravel
Intervention ImagePHP Image Processing
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.