Weave Code
Php Airbrake Bundle Laravel Package
ibrows/php-airbrake-bundle
A Symfony bundle that integrates the Airbrake PHP client, helping you send application exceptions and errors to Airbrake for monitoring, tracking, and reporting.
This helps binds the php-airbrake module into a Symfony2 bundle for easy use with the framework.
Frequently asked questions about Php Airbrake Bundle
- Can I install ibrows/php-airbrake-bundle in a Laravel application?
- No. ibrows/php-airbrake-bundle is a Symfony bundle: it registers a Bundle subclass, a DependencyInjection extension, and a kernel.exception event listener, none of which Laravel's container or package discovery understands. Laravel 9 through 11 pin Symfony 5, 6, or 7 components, while this bundle targets Symfony 2.3 to 2.8, so there is no autoloadable integration path. If you need Airbrake reporting in Laravel, use the maintained airbrake/phpbrake notifier behind your own service provider.
- Is ibrows/php-airbrake-bundle still maintained and safe for production?
- Treat it as abandoned. The repository shows 0 stars and 0 dependents, with no maintainer actively triaging issues or shipping fixes. Because the notifier sits directly in the request path, unvetted transitive dependencies become a real supply-chain concern. Do not add it to a new Laravel service.
- Which PHP and Symfony versions does this Airbrake bundle support?
- It targets the Symfony 2.3 to 2.8 era and the PHP versions current at that time, so it does not support PHP 8.x or modern Symfony releases, let alone Laravel 9 through 11. The kernel.exception listener also calls ExceptionEvent::getException(), which was removed in Symfony 4.x. Always check the composer.json PHP constraint before considering any reuse.
- What is the best Airbrake package for Laravel instead of this bundle?
- Use airbrake/phpbrake, the official maintained Airbrake PHP notifier that supports PHP 7.4 and 8.x. Bind it as a singleton in a service provider and route exceptions through Laravel's reporting hook, with a Monolog handler for non-exception error-level logs. If Airbrake is not mandated, sentry/sentry-laravel or bugsnag/bugsnag-laravel offer first-class Laravel support with Laravel-versioned releases.
- How do I report exceptions to Airbrake in Laravel 11?
- In Laravel 11 and later, call $exceptions->report(...) inside the withExceptions closure in bootstrap/app.php and forward the Throwable to your Airbrake notifier. On older versions, override the report method of App\Exceptions\Handler instead. Reporting through Laravel's native hook keeps capture working even when you customize error rendering, which the bundle's Symfony event listener cannot do.
- How much work is it to fork this bundle into a Laravel package?
- Budget roughly three to five engineering days before error data actually lands, before any test hardening. You would replace the DI extension with a service provider, replace YAML configuration with config/airbrake.php, and replace the kernel listener with a hook into Laravel's exception handler. Keep it a small, timeboxed ticket rather than a platform project.
- Should I use Airbrake, Sentry, or Bugsnag for a Laravel application?
- If Airbrake is contractually required, standardize on airbrake/phpbrake plus a thin Laravel service provider and a Monolog handler. If it is only an inherited artifact, sentry/sentry-laravel and bugsnag/bugsnag-laravel deliver the same outcome with maintained SDKs and releases aligned to Laravel versions. The integration layer is commodity; the decision worth making is which error backend your organization standardizes on.
- How do I stop Airbrake from receiving passwords, tokens, and session data?
- Scrub Authorization and Cookie headers, session identifiers, and query strings before transmission, since legacy notifiers commonly ship params and headers unfiltered. Add only the context you actually need, such as user identifier, route name, request ID, release or commit SHA, and environment. Do not rely on the bundle's automatic capture to do that filtering for you.
- Will a legacy Airbrake API key still work, or will error ingestion fail silently?
- Verify it before trusting it. This bundle posts to Airbrake's deprecated legacy key-based endpoints, where ingestion can fail silently and leave you believing you have coverage you do not. Confirm which Airbrake account generation you are on and test the notifier against the current notices API with a staging project key first.
- How can I test Airbrake error reporting in Laravel without polluting the dashboard?
- Bind a fake or logging double behind an interface in your test container, assert that exceptions reach it, and unit test the real notifier separately against a staging project key. Keep a test around your Monolog handler so non-exception error-level logs stay covered too. Avoid pointing CI at a live Airbrake project, since that inflates error volume and cost.
Weaver
How can I help you explore Laravel packages today?