Raven Bundle Laravel Package

Product Decisions This Supports

• Enhanced Error Transparency: Justify investment in user-facing error pages that reassure users while providing technical teams with actionable data (Sentry event IDs). Aligns with roadmap items for improved developer experience (DX) and customer trust.
• Build vs. Buy: Avoid reinventing the wheel for Sentry event ID display in Symfony error templates. This package eliminates custom dev effort (~1-2 dev days) and reduces technical debt.
• Incident Response: Support SOP documentation for debugging by embedding Sentry IDs in error pages, enabling faster triage (e.g., "Error Code: abc123" links directly to Sentry).
• Compliance/Transparency: Use case for regulated industries (e.g., fintech) where users must see error acknowledgment + technical identifiers for audits.
• Feature Flagging: Pair with a feature flag to toggle error ID visibility (e.g., disable in production for non-technical users, enable for admins).

When to Consider This Package

• Adopt if:

  • You use Symfony 2/3 + Sentry for error tracking and want zero-code integration for displaying event IDs in templates.
  • Your team prioritizes developer productivity over custom solutions (e.g., no time to build Twig extensions or PHP services).
  • You need quick wins for error pages (e.g., MVP launch, incident response improvements).
  • Your error pages are Twig-based (not Blade, PHP-only, or static HTML).

• Look elsewhere if:

  • You’re on Symfony 4+ (package is unmaintained; consider Sentry’s official Symfony integrations).
  • You need advanced error page customization (e.g., dynamic styling, multi-Sentry project support).
  • Your stack uses non-Symfony frameworks (Laravel, etc.) or non-Twig templating.
  • You require active maintenance (package is archived; evaluate risk of future compatibility breaks).
  • You’re using Sentry SDK v3+ (package may not support latest features like breadcrumbs or performance monitoring).

How to Pitch It (Stakeholders)

For Executives: "This package lets us show users a friendly error message while secretly giving our dev team a direct link to fix issues faster—no extra engineering work. For example, if a user sees ‘Error Code: abc123’, our team can instantly jump to Sentry to diagnose. It’s a 5-minute install that improves both user trust and incident response time, with zero ongoing cost. Given our [Symfony/Sentry] stack, this is a no-brainer for [Q1 roadmap item X]."

For Engineering: *"We can drop this into our Symfony app to automatically surface Sentry event IDs in error pages using a Twig function. Benefits:

• Zero custom code: No need to build a Twig extension or service.
• Reusable: Works across all error templates (e.g., 404, 500, custom pages).
• Lightweight: MIT-licensed, minimal dependencies, and archived but stable (last commit [YYYY]).
• Future-proof: If we migrate to Symfony 4+, we can replace it with Sentry’s official bundle. Tradeoff: Unmaintained, but since it’s a thin wrapper, risk is low. Let’s prototype it in [staging] this sprint."*

For Design/Product: *"This adds a subtle but powerful ‘we’re on it’ signal to users when errors occur. Example:

‘Oh no, something went wrong! The good news is our team has been notified (Error Code: abc123).’ We can:

• Hide the code for non-tech users (CSS/JS toggle).
• Style it to match our brand (e.g., grayed-out, tooltip on hover).
• A/B test visibility to see if it reduces support tickets. No design effort—just drop the Twig snippet into our existing error template."*