Weave Code
Symfony Messenger Queue Events Bundle Laravel Package
halloverden/symfony-messenger-queue-events-bundle
Symfony bundle that adds queue lifecycle events to Messenger. Hook into message dispatching, processing, success and failure to add logging, metrics or monitoring without touching your handlers. Works with any transport via the existing event dispatcher.
Dispatches additional events for symfony messenger
Frequently asked questions about Symfony Messenger Queue Events Bundle
- Can I use halloverden/symfony-messenger-queue-events-bundle in Laravel?
- No. This is a Symfony bundle built around Symfony's BundleInterface, dependency injection container, tagged services, and event dispatcher, and it depends on symfony/messenger rather than Laravel's queue system. Laravel does not boot Symfony bundles and uses Illuminate\Queue, so there is no automatic registration or configuration path. Using it would mean running a parallel Symfony Messenger bus inside Laravel, which is not recommended.
- What does this Symfony Messenger queue events bundle actually do?
- It adds queue lifecycle events to Symfony Messenger so you can hook into message dispatching, processing, success, and failure without editing handlers. The intent is logging, metrics, and monitoring across any Messenger transport via the existing event dispatcher. The provided overview does not list exact event class names or every lifecycle point, so verify those in source before relying on it.
- How do I install and register this bundle in Symfony?
- Install it with Composer using the package name, then register the bundle the normal Symfony way in bundles.php or your Kernel, depending on your Symfony version. Because the README excerpt is empty here, confirm the required symfony/framework-bundle or standalone wiring, configuration keys, and transport setup from the repository. Do not assume Laravel auto-discovery; none applies.
- Does halloverden/symfony-messenger-queue-events-bundle support Laravel 10 or Laravel 11?
- None is documented. This is not a Laravel package, has no Laravel service provider, and is not described as compatible with Laravel 10 or Laravel 11. For a Laravel 10 or 11 application, treat Laravel support as absent and use Laravel's native queue events instead.
- Which Messenger queue lifecycle events does this bundle dispatch?
- The overview says it dispatches events around message dispatching, processing, success, and failure. It does not specify event class names or whether it also covers transport send, consume, ack, reject, retry, or terminal failure. Read the source and tests to map each dispatched event to the exact Messenger point before adoption.
- How do I add logging and metrics to Laravel queues without this bundle?
- Use Laravel's native queue events such as JobQueued, JobProcessing, JobProcessed, JobFailed, JobExceptionOccurred, QueueBusy, and Looping. Register listeners in a dedicated QueueEventServiceProvider and add logging or metrics there. For Redis queues consider Horizon, and for tracing consider Telescope or an OpenTelemetry bridge.
- Is halloverden/symfony-messenger-queue-events-bundle production-ready and actively maintained?
- Treat it as high risk. The assessment reports 0 stars, 0 dependents, single-maintainer provenance, no adoption signal, and no evidence of security review or CI. Check last commit date, open issues, tagged releases, and maintainer responsiveness, and do not put it on a critical path.
- Which Symfony and PHP versions does this Messenger queue events bundle require?
- The provided context does not state Symfony 6 versus Symfony 7 constraints or the PHP floor. Verify composer.json for symfony/messenger, symfony/dependency-injection, and symfony/http-kernel requirements, and confirm whether Messenger is hard or suggested. Version constraints can block composer update, so check before any spike.
- Can a listener exception break message dispatching with this bundle?
- It is not established in the provided context whether listener exceptions are isolated from the dispatch path. If they are not, a throwing listener could break message publishing or processing. Test this explicitly with a deliberately failing listener in a non-production environment before adopting it.
- How should I test queue event listeners for Symfony Messenger or Laravel?
- For Symfony, test with an in-memory transport and a test event dispatcher or spy listeners, then assert the expected lifecycle events fire on dispatch, process, and failure; exact event classes must come from source. For Laravel, use Event::fake or Queue::fake and assert your QueueEventServiceProvider listeners receive native queue events. If you need maintained observability, prefer Laravel Horizon, Telescope, or an OpenTelemetry bridge over integrating this Symfony bundle.
Weaver
How can I help you explore Laravel packages today?