App Logger Laravel Package

Product Decisions This Supports

• Standardizing logging across RoadRunner-based applications to eliminate inconsistent log formats and reduce debugging time.
• Making a "buy vs build" decision by leveraging a pre-built, maintainable solution instead of developing custom logging infrastructure.
• Prioritizing observability on the product roadmap with structured logs that integrate with modern monitoring tools (ELK, Datadog, Loki).
• Enabling consistent per-request log context in long-lived worker processes, which is critical for distributed systems and microservices architectures.
• Justifying an investment in a RoadRunner v3 migration, since the 1.3.x line is the first to support RR v3 and confirms the package is actively maintained alongside the runtime.
• Forcing a dependency/upgrade planning decision — the package is now roadrunner/app-logger (renamed from the previous name), so composer constraints, service provider references, and internal docs must be updated as part of any PHP 8.2 upgrade.
• New in 1.3.1: Validating dependency hygiene before rollout — 1.3.1 corrects the RoadRunner dependency from spiral/roadrunner to roadrunner/roadrunner. Plan to adopt 1.3.1, not 1.3.0, so we don't inherit a constraint that pins the legacy spiral/* package namespace and complicates the RoadRunner v3 story.

When to Consider This Package

• ✅ Adopt if: Your stack uses RoadRunner PHP (now including RoadRunner v3), requires structured logs for aggregation, and needs consistent log context across long-lived workers.
• ✅ Adopt if: You are already on, or planning to move to, PHP 8.2+ — the 1.3.x line formally requires PHP 8.2, so teams on 8.0/8.1 must upgrade PHP before taking it.
• ✅ Target 1.3.1 specifically: It's a one-line dependency fix over 1.3.0 with no API changes, but it realigns us on roadrunner/roadrunner — the correct package for RoadRunner v3. Treat 1.3.1 as the minimum viable version for any new adoption.
• ⚠️ Plan the rename: Because the package was renamed to roadrunner/app-logger, treat 1.3.x as a breaking upgrade. Audit composer.json, lockfiles, CI configs, and any custom integrations for the old package name before rolling out.
• ⚠️ Check transitive constraints: If we still pull spiral/roadrunner elsewhere (older RR v2 bridges, framework integrations), Composer may resolve both namespaces side by side. Verify a clean composer why roadrunner/roadrunner / composer why spiral/roadrunner before rollout, and expect to retire the spiral/* dependency as part of the RR v3 migration.
• ❌ Look elsewhere if: You are on PHP 8.0/8.1 and cannot upgrade soon — stay on the 1.2.x line or evaluate a different logging integration until the PHP upgrade lands.
• ❌ Look elsewhere if: You are not running RoadRunner (e.g. FPM/Octane-only stacks); the package's core value — worker-aware context and RR integration — does not apply.
• ❌ Look elsewhere if: You need vendor-backed SLAs or a broad feature surface; this remains a focused, community-maintained integration. 1.3.0 was a maintenance/modernization release (test migration to Testo, static analysis cleanup, docs refresh) and 1.3.1 is a single dependency correction — not a feature expansion.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, low-risk dependency that keeps our logging consistent and observable across RoadRunner services, avoiding custom-built logging infrastructure. The 1.3.x line adds RoadRunner v3 support and moves the package to PHP 8.2, aligning us with a supported runtime and PHP baseline. Two planning items: a package rename (now roadrunner/app-logger), which is mechanical but breaking and should be scheduled alongside our PHP 8.2 upgrade, and a follow-up patch (1.3.1) that corrects which RoadRunner package we depend on. Net effect is a slightly cleaner dependency tree for the same effort — we simply pin 1.3.1 instead of 1.3.0.

For engineering: Upgrade path is 1.3.1 with PHP 8.2 required and RoadRunner v3 support; the package name changed to roadrunner/app-logger, so update composer requirements and any references. 1.3.1 is a pure bug fix over 1.3.0: it requires roadrunner/roadrunner instead of spiral/roadrunner, so it eliminates a legacy namespace constraint that would otherwise fight our RR v3 migration — no code or config changes beyond the version bump, but confirm nothing else in the tree still depends on spiral/roadrunner. 1.3.0 also migrated tests to Testo, resolved Psalm errors instead of suppressing them, and refreshed the README/installation docs — good signals of maintained code quality. Recommend pinning roadrunner/app-logger:^1.3.1, validating log output and request context in a staging worker, and confirming our monitoring pipeline (ELK/Datadog/Loki) still ingests the structured format before rollout.