- What does oxcom/symfony-rollbar-bundle actually do?
- It is a Symfony bundle that integrates Rollbar error monitoring into an application, reporting exceptions and logs through Symfony's service container. You configure the access token, environment, and handlers in bundle config, then use the injected logger like any other Symfony service. It is a thin, config-driven adapter that sits in the exception-handling and logging path rather than in business logic, so coupling is low.
- Can I use this Symfony bundle in a Laravel application?
- It is built as a Symfony bundle, so it does not ship a Laravel service provider or auto-discovery registration. Laravel has a dedicated first-party style integration in rollbar/rollbar-laravel, which is the more natural fit for a Laravel app. You can technically pull Symfony components into Laravel, but confirm the resolved dependency graph before committing, especially if other packages share the Symfony tree.
- How do I install and configure the bundle?
- Installation is a Composer require plus an access token supplied through environment configuration. No schema changes, queue setup, or data-store changes are required. The real effort is configuration reconciliation: diff the package's shipped config stub against your published config so you can see exactly which keys the bundle expects.
- How are errors routed to Rollbar with this bundle?
- A handler registered through the framework's error pipeline passes exceptions and log records to Rollbar. The main design decision is whether errors flow through the native handler or through a Monolog/Rollbar handler chain. You also choose whether reporting is synchronous or queued, which affects request latency versus delivery reliability.
- Does version 2.3.0 change the bundle configuration schema?
- The release notes state that bundle configuration was updated to handle the new Rollbar config, which suggests the accepted config schema shifted to track an upstream change. Key renames or re-nesting are the classic silent-failure case: the app boots and events still arrive, but context such as person, request, custom fingerprint, or scrub fields is dropped because the old keys are ignored. No migration note was provided, so treat the exact changes as unconfirmed until a staging install resolves them.
- Is upgrading to 2.3.0 a breaking change for my app?
- Both release note items are configuration-sensitive, and neither is described as breaking, but backward compatibility is unverified. If the package validates config strictly, an outdated config shape causes boot-time exceptions; if it does not, the failure is silent context loss. Do not upgrade in place on your primary branch: bump in a dedicated branch, resolve the lock file, and inspect what else moved in the dependency tree.
- What Symfony and PHP versions does this bundle require?
- The release notes mention deprecation notes being resolved to handle Symfony 4.2+ realization, which typically accompanies a minimum-dependency bump. That implies Symfony 4.2+ components may now be required, with knock-on minimum PHP and framework versions. The assessment was based on release note text only, so verify the actual floors against the package's composer.json before upgrading.
- How do I verify error context still reaches Rollbar after upgrading?
- Capture your live published config as-is, then diff it against the bundle's shipped config stub to surface renames and re-nesting. During transition, populate both legacy and new config keys simultaneously where the schema permits, so reporting survives either code path. Verify in staging against a dedicated Rollbar project or environment before touching production.
- Does the handler fail open or fail closed when Rollbar is unreachable?
- The supplied materials do not document this behavior, so it is an open question worth testing. Fail open means the report is dropped and the error is logged locally; fail closed means a misconfigured or unreachable Rollbar client can throw. Test both an invalid token and a blocked network path in staging, since the difference matters in production incident handling.
- What are the alternatives to this bundle for Rollbar in Laravel?
- For a Laravel application, rollbar/rollbar-laravel is the most direct option and registers itself through Laravel's package discovery. You can also route errors through a Monolog Rollbar handler if you already have a logging pipeline in place. If you are still evaluating vendors, Sentry via sentry/sentry-laravel and Flare are common alternatives with first-class Laravel support.