Register queue health monitoring - #2531
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe application registers Spatie’s queue health check without the previous five-minute failure threshold and schedules ChangesQueue health monitoring
Possibly related PRs
Merge Risk: ⚪ Minimal · up to This localized change registers and schedules queue health monitoring; no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Co-authored-by: Boy132 <Boy132@users.noreply.github.com>
Summary
QueueCheckwith a five-minute failure thresholdWhy
Pelican already uses Spatie Health for application monitoring, but the queue worker check was not registered or scheduled. This adds the smallest complete integration so stalled queue processing is visible through the existing health system.
This is part (b) of the work split out from #2529 following maintainer review.
Validation
vendor/bin/pint --test app/Console/Kernel.php app/Providers/AppServiceProvider.phpvendor/bin/phpstan analyse --no-progress app/Console/Kernel.php app/Providers/AppServiceProvider.phphealth:queue-check-heartbeatis registered by Artisanphp artisan schedule:listevery minute