Monitor Bundle Laravel Package

Product Decisions This Supports

• Platform versioning / roadmap pinning. v2.3.0 moves the floor to Symfony 7.4 LTS, which extends the supported window into roughly late 2029 (bug fixes to 2028, security to 2029). That is a multi-quarter planning constraint you can now write down rather than inherit accidentally.
• Reporting trust. The one functional change — unit timezone now passed to all Envelope instances — is a correctness fix for timestamped monitoring output. If any dashboard, SLA report, or customer-facing metric consumes this data, this release is the difference between "usable" and "quietly wrong in the wrong timezone."
• Build vs. buy for monitoring in the Novosga/queue domain. Adopting the bundle avoids reimplementing envelope-level monitoring plumbing. Building it yourself is only rational if you need metrics this bundle doesn't model.
• Maintenance-cost modelling. Dev tooling jumped to PHPStan 2 / PHPUnit 11 / PHPCS 4 and Symfony 7.4 deprecations were cleared. That's a signal the maintainer is keeping ahead of the next major, which lowers the odds of a forced migration landing on your team unplanned.
• A decision this release does not support: treating this as a Laravel observability choice. It is a Symfony bundle for the Novosga queue domain. If the product is Laravel-first, the honest answer is Pulse/Telescope/Horizon, and this package is a non-starter — worth stating plainly before it enters a comparison matrix.

When to Consider This Package

Adopt when:

• You run Novosga (or a Symfony 6.4/7.x application) and want its monitoring surface without custom work.
• You need Messenger Envelope-level instrumentation with per-unit timezone attribution.
• You can accept Symfony 7.4 LTS as a hard floor and the upgrade cadence that implies.
• Single-maintainer open source is acceptable risk for a non-critical-path component.

Look elsewhere when:

• The stack is Laravel-first. Pulling a Symfony bundle into a Laravel app to cover observability that Pulse/Horizon already covers is friction with no payoff.
• You need vendor SLAs, commercial support, or a named escalation path.
• You're pinned below Symfony 7.4 and can't move.
• You need general-purpose APM. This is domain-specific to queue management, not a broad observability layer.

How to Pitch It (Stakeholders)

Executives. Low-risk maintenance release, no breaking changes, no cost or licensing change. It puts us on Symfony 7.4 LTS — a longer support runway — and fixes a timezone bug that could have skewed any time-based reporting. One caveat worth flagging up front: this is a Symfony bundle for the Novosga queue domain, not a Laravel package. If we're standardizing on Laravel, this isn't our core observability tool and shouldn't be scoped as one.

Engineering. v2.3.0 is a hygiene-plus-one-fix release. Symfony 7.1 → 7.4 LTS, dev tooling bumped (PHPStan 2, PHPUnit 11, PHPCS 4), deprecations cleared ahead of Symfony 8, dependabot wired in. The functional change: unit timezone now propagates to every Envelope instance, so monitoring timestamps are correct per unit instead of falling back to a default — check whether downstream reports were assuming the old behavior. Single maintainer (@rogeriolino), no API changes, upgrade path looks clean. The only real constraint is the Symfony-native footprint.