Weave Code
Sentry Symfony Laravel Package
gcg-it/sentry-symfony
gcg-it/sentry-symfony integrates Sentry error tracking and performance monitoring into Symfony applications, offering automatic exception capture, request tracing, and configurable reporting through Symfony bundle and dependency injection setup to help teams diagnose production issues quickly.
Symfony integration for Sentry (http://getsentry.com)
Frequently asked questions about Sentry Symfony
- Can I use gcg-it/sentry-symfony in a Laravel application?
- No. gcg-it/sentry-symfony is a Symfony bundle that registers through config/bundles.php and hooks the Symfony HTTP kernel lifecycle; Laravel uses service providers, facades, and middleware, so none of the package's automatic capture fires. For Laravel 9, 10, or 11, use sentry/sentry-laravel instead.
- Why doesn't gcg-it/sentry-symfony capture exceptions in Laravel?
- Its exception, breadcrumb, and request-context capture depends on Symfony kernel events such as kernel.request and kernel.exception, and those events never run inside a Laravel request. The package has no Laravel service provider, facade, middleware, or publishable config, so it fails silently with no coverage. For observability, silent non-capture is the worst failure mode because teams only discover it during an incident.
- How do I install gcg-it/sentry-symfony?
- It is installed with Composer and registered in a Symfony app's config/bundles.php, then configured through the bundle's YAML extension. It is not a Laravel package and has no artisan install or config:publish workflow. If you are evaluating it for Laravel, stop and use sentry/sentry-laravel.
- Does gcg-it/sentry-symfony support Laravel 10 or Laravel 11?
- No. The package targets Symfony, not Laravel, and provides no Laravel-version-tagged releases or framework integration. Its symfony/* constraints may also collide with the versions pinned by a given laravel/framework major. Run composer why-not before considering any install, and use sentry/sentry-laravel for supported Laravel versions.
- What configuration does gcg-it/sentry-symfony require?
- It uses a Symfony bundle extension with YAML configuration for the Sentry DSN, error and trace sample rates, and optional Monolog handler wiring. There is no Laravel config file to publish and no environment-driven Laravel setup. In Laravel you would have to hand-wire Sentry\Client or Hub yourself, at which point the base sentry/sentry SDK or sentry/sentry-laravel is the correct dependency.
- What is the best Sentry package for Laravel instead of gcg-it/sentry-symfony?
- Use sentry/sentry-laravel. It provides a service provider, facade, exception-handler hook, queue and console instrumentation, scheduler support, Octane awareness, and releases tagged for Laravel versions. It is the defensible choice for Laravel 9, 10, and 11 and avoids the Symfony-only surface this package adds.
- Is gcg-it/sentry-symfony safe to use in production?
- Treat it as high risk. It has zero stars, zero dependents, and a description copied from the upstream tagline, which suggests an unreviewed agency fork of the official sentry/sentry-symfony bundle. Observability code sits on every request's hot path and often captures request bodies, headers, and breadcrumbs, so an unreviewed fork is a PII and supply-chain surface. There is no evidence of a patch cadence or security backports.
- How do I test Sentry error reporting after installing gcg-it/sentry-symfony?
- In a Symfony app, throw a deliberate test exception in staging and confirm the DSN, environment, release, and sample rates produce an event in Sentry. In Laravel, this package will not report because its Symfony kernel hooks never execute. Use sentry/sentry-laravel there and verify with a staged test exception before relying on it.
- What is the migration path from gcg-it/sentry-symfony to an official Sentry SDK?
- Split the dependency per application rather than forcing one package to serve both: Laravel services should use sentry/sentry-laravel, and Symfony services should use the official sentry/sentry-symfony bundle. If a team has forked this package for a local Symfony patch, rebase that patch onto the official bundle and let the fork die. Keep DSN, environment, release, and traces_sample_rate conventions consistent across services.
- Is gcg-it/sentry-symfony maintained, and which Symfony and PHP versions does it support?
- There is no visible evidence of maintenance, and the package has zero stars and zero dependents. Before adopting it, ask the vendor which upstream sentry/sentry-symfony branch it forked, what changed, the supported PHP, Symfony, and Sentry SDK matrix, the last release date, and the deprecation and patching owner. Until proven otherwise, dependency-risk review should assume no maintainer.
Weaver
How can I help you explore Laravel packages today?