- Can I install i22/airbrake-bundle in a Laravel application?
- No. i22/airbrake-bundle is a Symfony bundle built around Bundle subclasses, DependencyInjection extensions, and compiler passes, none of which exist in Laravel. Installing it alongside a modern Laravel app will almost certainly fail because of Symfony and PHP version constraints. For Laravel, use the underlying Airbrake notifier behind a service provider instead.
- Does i22/airbrake-bundle support Laravel 10 or Laravel 11?
- No. This bundle targets older Symfony 2.x and 3.x era projects with tight symfony/* and PHP constraints. Composer will likely refuse to install it alongside Laravel 10 or 11, which use Symfony 6 or 7 components and PHP 8.2 or newer. It is not a Laravel package and has no Laravel version support.
- What is the Laravel equivalent of this Airbrake bundle?
- The Laravel equivalent is a custom service provider that binds an Airbrake notifier as a singleton and registers a Monolog handler on the error or critical channel. That is roughly 150 lines of integration work. Read the bundle's config keys and handler wiring as a reference, then reproduce them with airbrake/airbrake-php or phpbrake.
- How do I install and configure i22/airbrake-bundle in Symfony?
- Install it with Composer, enable the bundle in AppKernel or bundles.php, and configure the Airbrake API key and environment settings. The bundle wires the notifier into the Symfony service container automatically. This installation path does not apply to Laravel applications.
- Is i22/airbrake-bundle maintained and safe for production?
- The project has zero stars and zero dependents, with no evidence of production validation or an active community debugging surface. It targets old Symfony versions and is unlikely to receive upstream fixes. Treat it as high project-health and vendor risk, and do not adopt it as a production dependency for Laravel.
- What are the alternatives to Airbrake for Laravel error monitoring?
- Common alternatives include Sentry, Flare, Bugsnag, and Honeybadger. Airbrake's PHP notifier is among the least-maintained major SDKs, and error monitoring has consolidated heavily toward Sentry. If Airbrake is already a sanctioned vendor, wire its notifier yourself, but evaluate budget, retention, and quota first.
- How do I test Airbrake exception reporting in a Laravel application?
- Use a fake or mocked notifier, trigger an exception in the test environment, and assert that your handler was called without hitting the real Airbrake API. Test your PII scrubbing filters and allowlists explicitly. For the Symfony bundle, use a test container and mock the Airbrake client in the same way.
- What production concerns come with Airbrake error reporting?
- Error payloads carry stack traces, request parameters, and often session or authentication context, so you must author and test scrubbing and allowlist configuration. Project keys are write-only ingest keys but still belong in secret storage, not the repository. Synchronous reporting in the request path can turn an Airbrake API slowdown into your own latency incident, so queue or async reporting is safer.
- Why is i22/airbrake-bundle considered out of scope for Laravel?
- Its entire value-add is Symfony-specific: a Bundle subclass, a DependencyInjection extension that hydrates the container from a config tree, and compiler passes that register an Airbrake client and Monolog handler. Laravel has no bundle, extension, or compiler-pass concept. The only transferable part is the wrapped notifier, which is an ordinary Composer library.
- What Guzzle or dependency conflicts should I check before adopting Airbrake in Laravel?
- phpbrake depends on Guzzle, so check its major version against everything else in the app, including AWS SDK, Stripe, and social auth packages. Guzzle 6 and 7 splits are a common source of Composer conflicts in Laravel estates. Also verify PHP and Symfony component constraints, and prefer airbrake/airbrake-php if Guzzle conflicts appear.