Weave Code
Messenger Monitor Bundle Laravel Package
karo-io/messenger-monitor-bundle
A Symfony bundle for monitoring Symfony Messenger: inspect queued, processing, and failed messages, track throughput, and review errors from a built-in dashboard so you can spot bottlenecks and retry failures without digging through logs or database tables.
Symfony bundle for informations about your Messenger queues and transports
Frequently asked questions about Messenger Monitor Bundle
- Is karo-io/messenger-monitor-bundle a Laravel package?
- No. It is a Symfony bundle built for Symfony Messenger and registers through config/bundles.php with a DependencyInjection extension class. Laravel has no bundle registry, so there is no supported way to load it as a normal Laravel package. Treat it as a Symfony-only component.
- Can I use karo-io/messenger-monitor-bundle with Laravel 10 or 11?
- Not in any supported way. Laravel 10 and 11 require PHP 8.1+, while this archived Symfony bundle is likely pinned to older Symfony and PHP versions, so Composer conflicts are probable. Even if you hand-wire its services into a Laravel service provider, Laravel's queue system is not Symfony Messenger, so the monitoring data would not map to Laravel's queues. Do not install it in a Laravel application.
- What does karo-io/messenger-monitor-bundle actually do?
- It provides a Symfony dashboard for Symfony Messenger transports and queues. It lets you inspect queued, processing, and failed messages, track throughput, and review errors so you can find bottlenecks and retry failures. It does not monitor Laravel queue drivers, Horizon, or the failed-jobs table.
- How do I install karo-io/messenger-monitor-bundle?
- In a Symfony application you would require it with Composer, register the bundle in config/bundles.php, and configure its DependencyInjection extension. There is no Laravel installation path because Laravel does not use Symfony's bundle registration system. For Laravel, use Horizon, php artisan queue:monitor, Telescope, or a Laravel-specific queue monitoring package instead.
- Does karo-io/messenger-monitor-bundle work with Laravel Redis, SQS, or database queues?
- No. It introspects Symfony Messenger transports, not Laravel queue drivers. Laravel's Redis, SQS, database, and Beanstalkd queues use a different model with jobs, queue:work, the failed-jobs table, and Horizon, so the bundle's metrics and failure views would not correspond to Laravel's operational reality. Use Horizon for Redis and queue:monitor plus the failed-jobs table for other drivers.
- What are the best Laravel alternatives to karo-io/messenger-monitor-bundle?
- For Redis queues, Laravel Horizon provides dashboards, metrics, and failed-job retries. For other drivers, php artisan queue:monitor plus the failed-jobs table and Laravel Telescope cover most visibility needs. Community packages such as laravel-queue-monitor are also available. For Symfony Messenger specifically, zenstruck/messenger-monitor-bundle is the actively maintained equivalent.
- Is karo-io/messenger-monitor-bundle maintained or abandoned?
- It is abandoned. The repository is archived, with roughly 14 stars and zero dependents, which means no security patches, no CVE response, and no compatibility fixes. Archived Symfony bundles of this vintage are often pinned to Symfony 4 or 5 and PHP 7.x, which conflicts with current Laravel 10 and 11 applications. Treat it as prior art rather than a dependency.
- Are there security risks in using karo-io/messenger-monitor-bundle?
- Yes, mainly because it is unmaintained and unvetted. Monitoring bundles often read transport DSNs and render queue contents, and Symfony bundles commonly auto-register routes and controllers; an unauthenticated endpoint could leak broker credentials or message payloads. With no upstream patches and little production exposure, any dependency it pulls in becomes an SBOM liability. Audit routes, authentication, and read-only behavior before considering any fork.
- Does karo-io/messenger-monitor-bundle add read load or expose routes in production?
- That is not documented or audited here. If the implementation polls brokers with non-passive calls or runs COUNT(*) on large message tables, it can degrade production backends. Symfony bundles also commonly expose console commands and HTTP routes, so verify authentication and read-only behavior before running it anywhere. The safest assumption is that you must review the code yourself.
- Can I fork karo-io/messenger-monitor-bundle and make it work with Laravel?
- Legally yes, because it is MIT licensed. Practically, you would own 100% of the code: you would need to rewrite the bundle's service wiring as a Laravel service provider and map Symfony Messenger concepts onto Laravel's queue model. That is a significant permanent maintenance burden for a capability Laravel already covers with Horizon, queue:monitor, Telescope, and the failed-jobs table. Fork only if you specifically need Symfony Messenger visibility and accept owning the fork.
Weaver
How can I help you explore Laravel packages today?