Symfony is supported via the sentry-symfony package as a native bundle.


Install the sentry/sentry-symfony package:

$ composer require sentry/sentry-symfony

Enabling the bundle

Enable the bundle in app/AppKernel.php:

class AppKernel extends Kernel
    public function registerBundles()
        $bundles = array(
            // ...

            new Sentry\SentryBundle\SentryBundle(),

        // ...

    // ...

Setting up the DSN

Add your DSN to app/config/config.yml:

    dsn: "___PUBLIC_DSN___"

If you’re using the Symfony Flex plugin, you’ll find this file already created for you; it will suggest using an environment variable to inject the DSN value securely.


The Sentry 2.0 SDK uses the Unified API, hence it uses the concept of Scopes to hold information about the current state of the app, and attach it to any event that is reported. This bundle has three listeners (RequestListener, SubRequestListener, and ConsoleListener) that add some easy default information. Those listeners normally are executed with a priority of 1 to allow easier customization with custom listeners, that by default run afterward, with a lower priority of 0.

Those listeners are final so not extendable, but you can look at those to know how to add more information to the current Scope and enrich you Sentry events.


This is an example of the bundle configuration with all the possible options and example values:

N.B. The register_error_listener and monolog configuration options are available since sentry/sentry-symfony:^3.2.0

    dsn: '___PUBLIC_DSN___'
    register_error_listener: true
            enabled: false
            level: DEBUG
            bubble: true
        attach_stacktrace: true 
        before_breadcrumb: '@sentry.callback.before_breadcrumb'
        before_send: '@sentry.callback.before_send'
        capture_silenced_errors: false
        context_lines: 5
        default_integrations: true 
        enable_compression: true
        environment: '%kernel.environment%'
        error_types: 'E_ALL & ~E_NOTICE'
        http_proxy: ''
          - '%kernel.cache_dir%'
          - '%kernel.project_dir%/vendor'
          - '@sentry.integration.my_custom_integration'
          - 'My\Exceptions\IgnorableException'
        logger: 'php'
        max_breadcrumbs: 50 
        max_value_length: 2048
          - '/local_dir/' 
        project_root: '%kernel.project_dir%'
        release: 'abcde12345'
        sample_rate: 1
        send_attempts: 3 
        send_default_pii: true 
        server_name: ''
          tag1: 'value1'
          tag2: 'value2'
        request: 1
        subrequest: 1
        console: 1


The DSN option is the only required option: it sets the Sentry DSN, and so reports all events to the related project. If it’s left empty, it disables Sentry reporting. Because Sentry enables the bundle in all environments, it’s recommended to disable it in the test and dev environments.


All the possibile configurations under the options key map directly to the correspondent options from the base SDK; you can read more about those in the Unified API configuration docs, and on the PHP specific SDK docs.

Below you can find additional documentation that is specific to the bundle usage, or information about the sensible default values that you can use in some cases.

before_breadcrumb and before_send

The before_breadcrumb and before_send options both accept a callable; thus, you cannot provide it directly through a YAML file; the bundle accepts a service reference (starting with @), which you can build in your DIC container.


The environment option defaults to the same environment of your Symfony application (For example,dev, test, prod…).


The in_app_exclude option is used to mark files as non belonging to your app’s source code in events’ stack traces. In this bundle it has two default values:

  • %kernel.cache_dir%, to exclude Symfony’s cache dir
  • %kernel.project_dir%/vendor, to exclude Composer’s dependencies


The project_root options defaults to %kernel.project_dir%.

Listener priorities

The listener_priorities options are used to change the priority at which the bundle’s listener is called. They all default to 1, so they are called just before the default priority of 0, at which you can easily add your custom listeners.