Kernel Laravel Package

Product Decisions This Supports

• Debugging & Developer Experience (DX):

  • Enable real-time debugging for complex Laravel applications without disrupting production workflows.
  • Build a self-service debugging panel for internal teams, reducing reliance on manual logs or external tools (e.g., Sentry, New Relic).
  • Accelerate bug triage by exposing structured debug data (requests, queries, collectors) in a centralized UI.

• Roadmap Prioritization:

  • Phase 1: Integrate as a developer-only feature (e.g., /debug endpoint) to replace ad-hoc logging.
  • Phase 2: Extend to monitoring dashboards for non-technical stakeholders (e.g., product teams tracking API failures).
  • Phase 3: Explore custom collectors for domain-specific metrics (e.g., payment processing, auth flows).

• Build vs. Buy:

  • Buy: Avoid reinventing a debugger lifecycle system (collectors, storage, PSR proxies). Justifies investment if the package aligns with Laravel’s ecosystem.
  • Build: Only if the package lacks critical features (e.g., no auth, no retention policies) or requires deep customization (e.g., integrating with existing observability tools).

• Use Cases:

  • Postmortems: Quickly replay failed requests with full context (headers, queries, middleware).
  • Performance Bottlenecks: Identify slow queries or external API calls via collectors.
  • Security Audits: Log sensitive data access patterns (e.g., failed auth attempts) without exposing raw logs.

When to Consider This Package

• Adopt if:

  • Your team uses Laravel and needs a lightweight, self-hosted debugging solution.
  • You prioritize developer velocity over enterprise-grade observability (e.g., no need for alerting/SLOs).
  • The package’s PSR proxy system fits your read-only data isolation needs (e.g., separating debug data from production logs).
  • You’re okay with low stars/score but see potential in its modularity (e.g., swapping collectors later).

• Look elsewhere if:

  • You need production-grade monitoring (e.g., uptime checks, synthetic transactions) → Use Laravel Scout + third-party tools.
  • Your stack includes non-Laravel services → Consider OpenTelemetry or Datadog APM.
  • You require compliance-ready data retention (e.g., GDPR) → The package may lack built-in policies.
  • Your team lacks PHP/Laravel expertise to customize collectors or storage backends.

How to Pitch It (Stakeholders)

For Executives:

"This package lets our Laravel devs debug 10x faster by centralizing request data, queries, and errors in a self-service panel—no more digging through logs or context-switching to external tools. It’s a low-cost, high-impact way to reduce toil in debugging, especially for complex flows like payments or auth. Think of it as ‘GitHub Copilot for debugging’: developers get instant context, and we avoid reinventing a debugger from scratch. ROI: Faster releases, fewer postmortems, and happier engineers."

For Engineering:

*"ADP Kernel gives us a modular debugger engine with:

• PSR-compliant proxies for read-only data isolation (safe for production-like environments).
• Custom collectors to instrument critical paths (e.g., slow queries, failed jobs).
• Laravel-native integration—no heavyweight APM overhead.

Tradeoffs:

• Not for production monitoring (use New Relic/Sentry alongside).
• Requires PHP/Laravel familiarity to extend (e.g., adding collectors).
• Early-stage (1 star), but the core architecture is sound for our needs.

Proposal: Pilot it for our [X] service’s debug panel, then decide if we fork or replace it with a commercial tool later."*