Laravel Query Logger Laravel Package

Product Decisions This Supports

• Observability and debugging investment: This package provides query logging for Laravel applications, supporting decisions about whether to build custom SQL/query observability or adopt a lightweight, focused package. It is most relevant for development, staging, and targeted production diagnostics rather than full APM replacement.
• Framework upgrade planning: v6.0.0 is a compatibility release tied to Laravel ^13.0 and PHP ^8.3. This directly informs roadmap sequencing: teams planning Laravel 13 adoption can standardize on v6; teams staying on Laravel 12 should remain on overtrue/laravel-query-logger:^5.1.
• Risk and maintenance assessment: The release adds 23 behavior tests, expands CI across PHP 8.3–8.5 and dependency graphs, enables Composer audit blocking, and makes PHPUnit fail on warnings/deprecations/risky tests. This improves confidence in the package as a low-cost buy-versus-build option.
• Production change management: Logging behavior and production source are unchanged, so the primary product decision is an upgrade/compatibility decision, not a functional migration. The exception is teams relying on the package in Laravel 13 environments, where v6 is required.
• Support matrix definition: Product and engineering can explicitly document supported Laravel/PHP combinations and avoid mixed-version support burden.

When to Consider This Package

• Consider v6.0.0 when the product is on, or actively migrating to, Laravel 13 and PHP 8.3+, and the team needs lightweight query logging for debugging, performance investigation, or development diagnostics.
• Consider it when the team wants a small, maintained package rather than building bespoke query logging around Laravel’s database events, especially if the package’s threshold filtering, SQL exclusions, request context, trigger sources, and log-channel configuration match the use case.
• Stay on ^5.1 if the application is on Laravel 12. Do not adopt v6 there; it is explicitly not compatible.
• Look elsewhere if the requirement is production-grade APM, distributed tracing, query plan analysis, historical performance dashboards, or alerting. This package is a logger, not a full observability platform.
• Treat the release cautiously if the organization requires zero known upstream notices in CI. The release notes disclose an upstream Symfony Translation/Carbon implicit-nullable deprecation on the lowest-secure PHP 8.4 graph; it is not suppressed. This is not a product blocker but should be understood by engineering.
• Note that the SQL interpolation fix in #71 is not included in v6.0.0. If that fix is required, confirm the release path before committing to v6.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, focused Laravel query-logging package. The new major version is primarily a compatibility release for Laravel 13 and PHP 8.3+. It does not change production logging behavior, and it strengthens test and CI coverage. Teams on Laravel 12 should stay on the prior 5.1 line, so there is no forced upgrade.

For engineering: v6.0.0 requires Laravel ^13.0 and PHP ^8.3. The release adds meaningful behavior-test coverage for real SQLite queries, bindings, thresholds, exclusions, log channels, and request context, plus broader CI across PHP 8.3–8.5 and dependency graphs. Production source and logging behavior are unchanged. The main adoption gate is framework version; Laravel 12 applications must remain on ^5.1. Be aware of the disclosed upstream Symfony Translation deprecation in the lowest-secure graph and that the #71 SQL interpolation fix is not included.