Bugsnag Psr Logger Laravel Package

Product Decisions This Supports

• Modern PSR-3/PSR-15 Compliance: Now supports PSR Log v3, ensuring future-proof integration with Laravel 10+ and PHP frameworks adopting the latest logging standards. This reduces friction for teams migrating to newer PHP versions or frameworks.
• Stronger Observability Stack: Aligns with BugSnag’s advanced error tracking while adhering to modern logging interfaces, enabling richer error context (e.g., structured metadata, exception chains) without custom work.
• Reduced Technical Debt: Eliminates legacy PSR-1 support, forcing teams to adopt current standards—reducing long-term maintenance overhead for logging infrastructure.
• Build vs. Buy: Reinforces the case for off-the-shelf observability by providing a maintained, standards-compliant solution, avoiding reinventing logging pipelines.
• Use Cases (Expanded):
  • Laravel 10+ or Symfony 6+ apps requiring PSR-3/PSR-15 compliance.
  • Microservices architectures needing consistent, standardized logging across services.
  • Compliance-heavy industries (e.g., fintech, healthcare) where structured error tracking is critical.
  • Teams adopting BugSnag’s newer features (e.g., Breadcrumb, Release Tracking) via PSR-3 integration.

When to Consider This Package

• Adopt if:
  • Your team uses BugSnag for error monitoring and needs PSR-3/PSR-15 compliance (e.g., Laravel 10+, Symfony 6+, or PHP 8.1+).
  • You’re migrating from PSR-1 or want to future-proof your logging stack.
  • You prioritize automated, structured error reporting with minimal custom code.
  • Your stack includes Monolog, Laravel’s built-in logger, or other PSR-3-compliant loggers.
  • You need rich error context (e.g., stack traces, custom metadata) without manual instrumentation.
• Look elsewhere if:
  • You require PSR-1 support (use v1.0 of this package or a different tool).
  • Your team cannot upgrade to PSR-3/PSR-15 (e.g., legacy PHP 7.4 or non-compliant frameworks).
  • You need real-time log streaming (e.g., for live debugging) and rely on raw log output (e.g., ELK/Splunk).
  • You’re all-in on open-source and cannot use BugSnag’s proprietary features (e.g., error grouping, dashboards).
  • Your app extends Bugsnag’s internal classes (breaking changes in v2.0.0 may require refactoring).

How to Pitch It (Stakeholders)

For Executives: "This updated package (v2.0.0) ensures our PHP/Laravel apps use modern logging standards (PSR-3/PSR-15), cutting debugging time by surfacing errors directly to BugSnag with richer context. It’s a zero-maintenance upgrade that aligns with our SRE goals and avoids custom logging work. The shift to PSR-3 also future-proofs our stack for Laravel 10+ and PHP 8.1+."

For Engineering: "BugSnag’s PSR-3 logger (v2.0.0) is now fully aligned with modern PHP frameworks—no more PSR-1 hacks. It’s a drop-in replacement for Monolog/Laravel logging, adds type safety, and unlocks BugSnag’s latest features (e.g., better breadcrumbs, release tracking). If you’re on Laravel 10+ or Symfony 6+, this is the recommended way to integrate BugSnag. Note: If you’re extending BugsnagLogger or MultiLogger, you’ll need to refactor due to breaking changes (e.g., removed AbstractLogger wrapper)."