Weave Code
Sentry Bundle Laravel Package
kunstmaan/sentry-bundle
Integrates Sentry error tracking into Kunstmaan CMS and bundle-based Symfony applications, capturing exceptions and reporting them to your Sentry project so you can monitor, debug, and resolve production issues faster.
THIS REPO IS DEPRECATED: replaced by Monolog | The SentryBundle for Symfony2 helps binds the raven-php module into a Symfony2 bundle for easy use with the framework. It will autoload an exception handler into the framework, so that all uncaught errors are sent to a Sentry server.
Frequently asked questions about Sentry Bundle
- Is kunstmaan/sentry-bundle compatible with Laravel?
- No. kunstmaan/sentry-bundle is a Symfony2 bundle that relies on Symfony's bundle, dependency-injection, and event-dispatcher conventions, not Laravel's service container or bootstrapping model. There is no drop-in path for Laravel, and any integration would require writing your own service provider and exception-handler registration around the legacy raven-php client. At that point the bundle contributes nothing, and sentry/sentry-laravel is the native, maintained solution.
- How do I install kunstmaan/sentry-bundle?
- It is installed with Composer as kunstmaan/sentry-bundle and then registered as a bundle in a Symfony2 AppKernel, where it wires raven-php into the service container and autoloads an exception handler. That installation model is Symfony-specific and does not translate to Laravel. Because the repository is explicitly deprecated, new installs are not recommended.
- Why is kunstmaan/sentry-bundle deprecated?
- The repository description states that it is deprecated and replaced by Monolog. The underlying raven-php SDK is the pre-2.0 Sentry client, and Sentry has retired the legacy authentication mechanism those clients use. Against current Sentry SaaS and modern self-hosted releases, a raven client will typically fail to authenticate rather than degrade gracefully.
- What should I use instead of kunstmaan/sentry-bundle for Sentry in Laravel?
- Use sentry/sentry-laravel on top of the current sentry/sentry SDK. It is framework-native, providing a service provider, exception-handler registration, breadcrumbs, performance tracing, release and commit tagging, and sampling. For Symfony applications, use the maintained Symfony Sentry bundle or a Monolog handler rather than this deprecated bundle.
- Does kunstmaan/sentry-bundle still work with current Sentry servers?
- Most likely not. The bundle depends on raven-php, the legacy pre-2.0 Sentry client, and Sentry has retired the legacy authentication mechanism that client uses. Against current Sentry SaaS or recent self-hosted releases, authentication will typically fail, so the package does not simply degrade—it usually does not function.
- Which PHP and Laravel versions does sentry/sentry-laravel support?
- Modern sentry/sentry-laravel sets a floor around PHP 7.2 and Laravel 5.7 and supports current Laravel releases. If your application is on older PHP, the constraint is your platform rather than the Sentry choice. Confirm your PHP and Laravel versions before planning the migration.
- Is kunstmaan/sentry-bundle safe to run in production?
- It is not recommended for production. The package has no maintenance, so there is no CVE response, and an exception handler sits on the error path of every request—a privileged position that makes shipping unpatched code a governance issue. Old raven clients also predate mature before_send-style scrubbing and breadcrumb controls, so raw exception payloads with stack traces and request context may be sent without a scrubbing hook.
- How does kunstmaan/sentry-bundle capture uncaught exceptions?
- It autoloads an exception handler into the Symfony2 framework via AppKernel boot, so uncaught errors are sent to a Sentry server through raven-php. The bundle's value is delivered entirely through Symfony's bundle, DI, and event-dispatcher conventions. Laravel's bootstrapping model is structurally different, so the same autoloaded-handler idea must be implemented through a Laravel service provider instead.
- How many projects depend on kunstmaan/sentry-bundle?
- The package has zero direct dependents and roughly 21 stars, so there is no ecosystem evidence of anyone running it successfully today. That means no field-tested failure modes, no Stack Overflow corpus, and no community patches. Any integration work would be bespoke and unsupported.
- What are the alternatives to kunstmaan/sentry-bundle for Symfony and Laravel?
- For Laravel, use sentry/sentry-laravel with the current sentry/sentry SDK. For Symfony, use the maintained Symfony Sentry bundle or a Monolog handler, which is the successor direction named in the deprecation notice. If the package appears only as a transitive dependency, plan its removal rather than adopting it.
Weaver
How can I help you explore Laravel packages today?