Symfony Doctrine Sql Logger Bundle Laravel Package

Product Decisions This Supports

• Observability feature decisions: Informs whether to add richer SQL query logging (parameters, timing, context) to a Symfony/Doctrine service before investing in a full APM tool.
• Build vs. buy: For Symfony apps already on Doctrine DBAL, adopting this MIT bundle is a low-cost alternative to building custom query logging; for Laravel/Eloquent apps, the equivalent build/buy decision should target Laravel Telescope, Debugbar, or DB::listen() instead.
• Roadmap prioritization: Helps decide whether SQL observability is a “quick win” for developer productivity or a larger platform investment requiring production-grade tracing, sampling, and PII controls.
• Use-case validation: Appropriate for local/staging debugging, performance triage, and incident root-cause analysis; weaker fit for compliance-grade audit logging unless parameter redaction and retention are addressed.
• Dependency strategy: Signals a “small utility, vendor/fork if needed” decision rather than a strategic platform dependency, given very low adoption (3 stars, 0 dependents).

When to Consider This Package

• You run Symfony with Doctrine DBAL and need better SQL logs than the default stack provides.
• You want query parameters, timing, and contextual logging without standing up a full APM platform.
• Your team is comfortable with a small, low-adoption MIT dependency and will pin/review/fork it if necessary.
• You need a time-boxed spike for developer debugging, not a long-term vendor-supported observability platform.
• Look elsewhere if you are on Laravel/Eloquent—this is a Symfony bundle, not a Laravel package, and will not integrate out of the box.
• Look elsewhere for production-grade APM, distributed tracing, compliance audit logging, PII-safe query capture, or vendor-backed SLAs.

How to Pitch It (Stakeholders)

• Executives: A low-cost MIT utility that can speed up SQL debugging for Symfony/Doctrine services; it is not a platform bet and carries minimal license cost, but also minimal adoption evidence.
• Engineering: A small, focused bundle that improves Doctrine DBAL query visibility; suitable for a short POC in non-production. Confirm maintenance status, Symfony/Doctrine version compatibility, and parameter redaction before broader use.
• Recommendation: Treat it as a tactical developer-productivity experiment for Symfony teams only; do not position it as a Laravel solution or a strategic observability investment.