Airbrake Bundle Laravel Package

Product Decisions This Supports

• Framing check first: this is not a Laravel package. eo/airbrake-bundle is a Symfony2 bundle (AppKernel registration, config.yml tree, DI extension). If the roadmap item is "add error tracking to our Laravel app," this package answers a question we aren't asking. The decision it does support is narrower: how to instrument a legacy Symfony 2.1–2.8 application we still operate.
• Choose the destination, not the notifier. The only real product surface here is api_key, host, async, secure, and ignored_exceptions. That makes the decision Airbrake.io SaaS vs. self-hosted Errbit — a real PM call on time-to-value, ops burden, data residency, and per-event pricing. Errbit's Airbrake-v2 compatibility means we can defer this choice and still start capturing exceptions.
• Set the alerting policy deliberately. Error monitoring ROI is decided by noise, not coverage. The ignored_exceptions list is where we encode "what deserves a page" — 404s and access-denied out, real failures in. Getting this wrong trains the team to ignore alerts.
• Scope the effort honestly. The capability is ~a day of glue: register the notifier, set environment, ignore list, and release marker. That supports a "buy the vendor, own the glue" decision over adopting a stale dependency.
• Fit to use cases: low-traffic Symfony 2.x apps, internal tools, and in-flight legacy migrations where the framework version pins us to era-appropriate packages — not new Laravel services.

When to Consider This Package

Adopt only if all of these hold:

• The target application is Symfony 2.1+. There is no Laravel service provider, no config/app.php registration, no facade — despite being filed here as a Laravel package.
• Airbrake.io or self-hosted Errbit is already the chosen backend.
• We are on a legacy Symfony stack where a modern notifier's dependency tree won't resolve.
• We accept ownership. Last release 2016-11-16, 5 stars, 0 dependents. Treat it as vendored source, not a dependency: budget for patching PHP 8 deprecations and Airbrake API drift with no upstream fix.

Look elsewhere when:

• Any Laravel application. Use Airbrake's official PHP notifier with its Laravel integration, or evaluate Sentry / Flare / Inspector. Bridging a Symfony bundle into Laravel is pure maintenance tax.
• Symfony 3.4+/5/6/7. Wire the maintained Airbrake PHP notifier via a service definition instead.
• PHP 7.4+/8.x. Verify Composer resolution before anything else; this predates it.
• We need more than exception forwarding — tracing, breadcrumbs, per-release regression detection, user context. This is exception-only.
• We already own Sentry / Bugsnag / Rollbar. Then this is a duplication decision, not an integration one.

A note on scoring: the high opportunity signal reflects unmet demand for Airbrake/Errbit glue in this niche, not a reason to adopt a stale package. The demand is the insight; the package is not the answer.

How to Pitch It (Stakeholders)

Executives. We need production failures visible before customers report them. That splits into two decisions: the destination (Airbrake SaaS vs. self-hosted Errbit) and the glue code that connects it. This package is a 2016-era Symfony bundle with five stars and zero dependents — it is a useful reference for how small the integration is, not a strategic asset. Recommendation: pick the destination, staff the integration (~1 day), and decline to add this package as a dependency unless we operate a legacy Symfony 2.x app, in which case we pin a release and own the fork.

Engineering. For our Laravel work this is the wrong tool: Symfony-only and unmaintained since 2016. The equivalent effort is registering the official notifier and setting four things — api_key, environment, ignored-exception list, release marker. One PR, no new long-lived dependency. If a legacy Symfony 2.x app is in scope, pin a tagged release (never dev-master), confine it to that app, and confirm Errbit is the runtime target since the Airbrake v2 payload contract is terminal on hosted Airbrake.io.

Ask. Decide SaaS vs. self-hosted Errbit this sprint; ship the notifier with production-only reporting, a curated ignore list, and a release tag; revisit vendor consolidation at the next platform review rather than piecemeal.