Weave Code
Sentry Bundle Laravel Package
practo/sentry-bundle
A Laravel bundle that integrates Sentry error tracking into your application, helping you capture exceptions, log errors, and monitor application health from a centralized dashboard. Simple to install and configure.
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 practo/sentry-bundle compatible with Laravel?
- No. practo/sentry-bundle is a fork of a Symfony2 bundle that wires legacy raven-php into Symfony's kernel and error-handling lifecycle, and it does not provide a Laravel service provider, facade, auto-discovery, or Laravel-native exception handler integration. For a Laravel application, use sentry/sentry-laravel instead.
- How do I install practo/sentry-bundle in a Laravel application?
- You can add it with Composer, but installation alone will not make it work in Laravel because there is no Laravel package discovery or service provider. The bundle expects Symfony2 bundle registration and configuration. For Laravel, install and configure sentry/sentry-laravel rather than trying to bridge this Symfony2 bundle.
- Does practo/sentry-bundle support Laravel auto-discovery?
- No. It is a Symfony2 bundle and does not declare Laravel auto-discovery or a Laravel service provider. Laravel will not register its error handler or configuration automatically. You would need custom bridging, which is not recommended for a new Laravel integration.
- Which Laravel versions and PHP versions does practo/sentry-bundle support?
- It does not target Laravel versions at all; its upstream assumptions are Symfony2 and legacy Raven SDK constraints. PHP and Symfony compatibility should be checked against the package's Composer file before any spike, but there is no documented Laravel support matrix. For supported Laravel and PHP versions, refer to sentry/sentry-laravel.
- Can practo/sentry-bundle replace Laravel's exception handler?
- No. The package autoloads a Symfony2-oriented exception handler and does not integrate with Laravel's default exception handler. Trying to combine them risks conflicting error handlers and unpredictable reporting or logging behavior. Use the official Laravel SDK, which is designed to hook into Laravel's exception handling cleanly.
- What is the best alternative to practo/sentry-bundle for Laravel?
- The official sentry/sentry-laravel package is the recommended alternative for Laravel applications. It provides Laravel service provider integration, configuration publishing, exception reporting, and support for modern Sentry SDK features. For modern Symfony, use sentry/sentry-symfony; practo/sentry-bundle is only relevant to legacy Symfony2 setups.
- Does practo/sentry-bundle work with the modern Sentry PHP SDK?
- It is built around legacy raven-php rather than the modern sentry/sentry PHP SDK. That legacy protocol and API surface may be deprecated or incompatible with current Sentry server expectations. Validate any current usage with a time-boxed spike, and prefer the official SDK for new work.
- How do I configure the Sentry DSN, environment, and sampling with practo/sentry-bundle?
- Configuration is handled through Symfony2 bundle configuration, not Laravel config publishing or .env-driven Laravel config files. DSN, environment tagging, and sampling options depend on the legacy Raven integration and must be verified against the bundle's config. In Laravel, sentry/sentry-laravel exposes these through Laravel configuration and environment variables.
- Is practo/sentry-bundle maintained and safe for production Laravel use?
- It has zero stars, zero dependents, and appears to be a minor fork with little community validation or clear ownership. For production Laravel use, it carries high risk around abandoned upstream dependencies, deprecated Raven patterns, and conflicts with Laravel's error handling. Treat it as unsupported for Laravel and use the official SDK unless you have a legacy Symfony2 constraint and an internal owner.
- How should I test practo/sentry-bundle before using it in production?
- First confirm whether your target is actually a legacy Symfony2 application, because a Laravel proof of concept is not a good fit. If you must evaluate it, run a time-boxed spike in a non-production branch with representative exceptions, DSN configuration, and failure-mode checks. Document rollback behavior and compare the results against sentry/sentry-laravel or sentry/sentry-symfony before adopting it.
Weaver
How can I help you explore Laravel packages today?