PHPackages                             eurekos/symfony-messenger-monitor - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Queues & Workers](/categories/queues)
4. /
5. eurekos/symfony-messenger-monitor

ActiveSymfony-bundle[Queues & Workers](/categories/queues)

eurekos/symfony-messenger-monitor
=================================

A simple Symfony bundle to view the current Messenger queue.

v0.1.0(1mo ago)02↓85.7%MITPHPPHP >=8.1

Since Jun 5Pushed 1mo agoCompare

[ Source](https://github.com/eurekos/symfony-messenger-monitor)[ Packagist](https://packagist.org/packages/eurekos/symfony-messenger-monitor)[ RSS](/packages/eurekos-symfony-messenger-monitor/feed)WikiDiscussions main Synced 1w ago

READMEChangelogDependencies (6)Versions (2)Used By (0)

Eurekos Symfony Messenger Monitor
=================================

[](#eurekos-symfony-messenger-monitor)

A Symfony bundle to view the current Symfony Messenger queue in the browser.

What it does:

- Lists every configured Messenger transport and how many messages are waiting.
- Shows the messages currently sitting on a transport (message id, message class and stamps), without consuming them.

It relies on Symfony Messenger's [`ListableReceiverInterface`](https://symfony.com/doc/current/messenger.html), so messages are only listable for transports that implement it (e.g. Doctrine, the in-memory transport, and Redis on recent Symfony versions). Transports that don't support listing (e.g. AMQP, SQS) are still shown, with a message count when the transport can provide one.

Requirements
------------

[](#requirements)

- PHP 8.1+
- Symfony 6.4, 7.x or 8.x (`symfony/messenger` + `symfony/twig-bundle`)

Installation
------------

[](#installation)

```
composer require eurekos/symfony-messenger-monitor
```

If you don't use Symfony Flex, register the bundle manually in `config/bundles.php`:

```
return [
    // ...
    Eurekos\SymfonyMessengerMonitor\EurekosSymfonyMessengerMonitorBundle::class => ['all' => true],
];
```

Setup
-----

[](#setup)

This bundle ships an **abstract** controller. You enable the monitor by extending it in your own application: you choose the path prefix and the access control, and the routes are inherited from the base controller.

Create `src/Controller/MessengerMonitorController.php`:

```
namespace App\Controller;

use Symfony\Component\Routing\Attribute\Route;
use Symfony\Component\Security\Http\Attribute\IsGranted;
use Eurekos\SymfonyMessengerMonitor\Controller\MessengerMonitorController as BaseMessengerMonitorController;

#[Route('/admin/messenger')] // path prefix for the controllers
#[IsGranted('ROLE_ADMIN')]   // alternatively, protect it with a firewall
final class MessengerMonitorController extends BaseMessengerMonitorController
{
}
```

That's it. With the default Symfony route configuration (which loads attribute routes from `src/Controller/`), this registers:

Route namePath`eurekos_messenger_monitor_index``/admin/messenger``eurekos_messenger_monitor_transport``/admin/messenger/transport/{name}`The monitor is then available at `/admin/messenger`.

### Notes

[](#notes)

- The base controller is autowired into your subclass automatically (it needs Twig and an internal transport service, both provided for you). You don't declare a constructor unless you want to.
- Create **exactly one** subclass. The route names are defined on the base controller's actions, so several subclasses would clash.
- Don't set a `name:` prefix on the class-level `#[Route]` attribute, otherwise the internal template links (which use the route names above) won't resolve.
- If you prefer a firewall to `#[IsGranted]`, drop the attribute and guard the prefix instead:

    ```
    # config/packages/security.yaml
    access_control:
        - { path: ^/admin/messenger, roles: ROLE_ADMIN }
    ```

This bundle adds **no** access control of its own; the queue can expose sensitive data, so always protect your route.

How it works
------------

[](#how-it-works)

At compile time the bundle collects every service tagged `messenger.receiver`(that is how Symfony registers transports) into a service locator keyed by transport name. The controller then asks each receiver for its message count (`MessageCountAwareInterface`) and, when supported, lists pending envelopes (`ListableReceiverInterface::all()`).

License
-------

[](#license)

MIT. See [LICENSE](LICENSE).

###  Health Score

34

—

LowBetter than 75% of packages

Maintenance90

Actively maintained with recent releases

Popularity2

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity32

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Unknown

Total

1

Last Release

49d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/35bc0bb35837e6defd32d8cc3335ea8257446ec734f0bf6aa9c79feb6981285d?d=identicon)[pavloshevchuk](/maintainers/pavloshevchuk)

---

Top Contributors

[![pavloshevchuk](https://avatars.githubusercontent.com/u/10268035?v=4)](https://github.com/pavloshevchuk "pavloshevchuk (2 commits)")

---

Tags

symfonybundlequeuemonitorMessenger

### Embed Badge

![Health badge](/badges/eurekos-symfony-messenger-monitor/health.svg)

```
[![Health](https://phpackages.com/badges/eurekos-symfony-messenger-monitor/health.svg)](https://phpackages.com/packages/eurekos-symfony-messenger-monitor)
```

###  Alternatives

[shopware/core

Shopware platform is the core for all Shopware ecommerce products.

585.6M600](/packages/shopware-core)[sylius/sylius

E-Commerce platform for PHP, based on Symfony framework.

8.5k5.9M754](/packages/sylius-sylius)[sulu/sulu

Core framework that implements the functionality of the Sulu content management system

1.3k1.4M215](/packages/sulu-sulu)[shopware/platform

The Shopware e-commerce core

3.4k1.5M3](/packages/shopware-platform)[easycorp/easyadmin-bundle

Admin generator for Symfony applications

4.3k17.9M400](/packages/easycorp-easyadmin-bundle)[shopware/storefront

Storefront for Shopware

674.6M247](/packages/shopware-storefront)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)