Symfony Messenger Queue Events Bundle Laravel Package

Product Decisions This Supports

• Framework-fit triage: Despite the "Laravel/PHP" framing, this is a Symfony Messenger bundle, not a Laravel package. The first PM decision it enables is a fast "no" for Laravel-based products and a "maybe" for Symfony services already using Messenger with async transports.
• Build vs. buy for queue observability: It dispatches additional events around Messenger message lifecycle (dispatch/consume outcomes), which is the cheap path to audit trails, throughput/latency metrics, and failure alerting without instrumenting every handler or message class.
• Roadmap for ops/observability features: Unlocks backlog items like per-message SLA tracking, dead-letter/rejection auditing, tenant-level queue activity reporting, and "who triggered this job" compliance logging — all as subscribers to these events rather than core code changes.
• Reduced coupling in feature design: Teams can attach cross-cutting behavior (metrics, logging, retry bookkeeping, notifications) to queue lifecycle events instead of editing handlers, which shortens delivery time for cross-cutting roadmap items and lowers regression risk.
• Make-vs-fork call: MIT license plus tiny surface area means a PM can approve vendoring/forking it as an internal shim if maintainership stalls, rather than blocking a roadmap item on an upstream release.

When to Consider This Package

• The service is Symfony and already uses Symfony Messenger with async transports (AMQP, Redis, Doctrine, SQS).
• You need lifecycle hooks for observability, compliance auditing, or metrics without touching message handlers — and you're prepared to own the integration, since there is no first-party support.
• The requirement is additive and non-critical-path: event emission for logging/metrics. It should never be the mechanism your queue's correctness depends on.
• You accept vendor risk: 0 stars, 0 dependents, score 0. Treat it as "small MIT utility to evaluate and likely vendor," not a dependency with a support contract. Read the source (it should be a thin compiler-pass + event dispatcher) and pin the version.
• Look elsewhere when: you're on Laravel (use Laravel's native queue/job events, JobProcessing/JobProcessed/JobFailed, or Horizon for metrics); when standard Symfony Messenger events and middleware already cover the need; when you require vendor-backed support or a maintained project with a release cadence; or when you need deep, production-grade tracing — buy Datadog/Sentry/OpenTelemetry instrumentation instead of assembling it from a zero-adoption bundle.
• Disqualifier: no public adoption history means no battle-testing; don't put it in front of high-volume queues without a staged rollout in staging first.

How to Pitch It (Stakeholders)

Executives: A small, free (MIT) add-on for our Symfony services that lets us see what happens to every queued message — when it's sent, consumed, and fails — without rebuilding our job code. It supports audit and reliability reporting on the roadmap at near-zero license cost. The tradeoff is that it's an unproven open-source utility with no user base, so we'd vendor it internally and own it; it's a two-day integration, not a platform bet.

Engineering: This is a Symfony Messenger bundle that emits extra events around message lifecycle, so we can implement logging, metrics, and audit subscribers instead of sprinkling that logic through handlers. It's additive and easy to remove. Caveats: it's not a Laravel package, so it's irrelevant to our Laravel services; it has zero stars/dependents, so we review the source, pin the version, and fork it if needed. It complements — does not replace — real APM/observability tooling.