Propel Logger Bundle Laravel Package

Product Decisions This Supports

• Debugging & Performance Optimization: Accelerates root-cause analysis for slow Propel ORM queries by exposing full stacktraces and duplicate query detection in the Symfony Profiler. Critical for teams relying on Propel for complex data operations.
• Dev vs. Prod Tradeoff: Justifies a "build vs. buy" decision by eliminating custom logging logic, reducing technical debt, and improving developer velocity during debugging phases.
• Roadmap for Observability: Enables deeper query-level insights for future performance monitoring tools (e.g., integrating with APM systems like New Relic or Datadog).
• Use Cases:
  • Legacy Symfony 2.x applications with Propel ORM.
  • Teams struggling with opaque query performance (e.g., nested joins, N+1 queries).
  • Pre-release environments where query debugging is prioritized over production overhead.

When to Consider This Package

• Avoid if:
  • Using Symfony 3+ or Doctrine ORM (incompatible; consider stof/doctrine-extensions or web-profiler).
  • Production environments (disable in prod via require-dev; overhead may impact performance).
  • Modern stacks (Symfony 5/6+ with Propel 2.x may need alternative solutions like propel/propel’s built-in logging).
  • Alternative tools exist: For broader ORM support, evaluate symfony/profiler + custom listeners or blackfire/php.
• Consider if:
  • Debugging Propel queries is a blocker for feature velocity.
  • Team lacks expertise in SQL optimization or Propel internals.
  • Symfony 2.x is long-term maintained (e.g., legacy enterprise apps).

How to Pitch It (Stakeholders)

For Executives: "This bundle turns Propel’s ‘black box’ queries into actionable insights—like a flight recorder for SQL. For every slow endpoint, we’ll see exactly which queries are duplicated or inefficient, cutting debugging time by 50%. Low risk (dev-only), high ROI for legacy systems. Comparable to hiring a SQL expert on demand."

For Engineering: *"Symfony Profiler now surfaces Propel query stacktraces with file/line context—no more guessing where Model::findAll() explodes. Zero config for basic use; just whitelist namespaces. Perfect for:

• Onboarding: New devs ramp up faster.
• Refactoring: Identify query bottlenecks before optimizing.
• Legacy Tech Debt: Justify Propel’s continued use with data-backed performance stories. Downside: ~5% overhead in dev (disable in prod). Tradeoff: faster fixes vs. marginal perf cost."*

For DevOps/SRE: *"No infrastructure changes—pure PHP logging. Integrates with existing Symfony Profiler, so no new dashboards. Critical for:

• Incident Response: Pinpoint Propel queries in slow API calls.
• Cost Savings: Reduces need for manual query logging or external tools. Caveat: Not for production; align with your observability strategy (e.g., log aggregation)."*