4.9.2

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.9.2.

Bug Fixes

• We decided to revert two previous PRs that aimed to remove deprecation warnings during test runs (#736)

  • Revert: Add a new Doctrine DBAL tracing driver that does not implement the deprecated VersionAwarePlatformDriver (#723)
  • Revert: Fix a regression in TracingDriverForV32 by adding VersionAwarePlatformDriver::createDatabasePlatformForVersion (#731)

We are sorry for the inconvenience caused by these changes.

4.9.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.9.1.

Bug Fixes

• Fix a regression in TracingDriverForV32 by adding VersionAwarePlatformDriver::createDatabasePlatformForVersion (#731)

4.9.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.9.0.

Features

• Add a new Doctrine DBAL tracing driver that does not implement the deprecated VersionAwarePlatformDriver (#723)

  The driver is automatically picked if doctrine/dbal version 3.2.0 or higher is installed.

Bug Fixes

• Fix config type of http_connect_timeoutand http_timeout options (#721)

Misc

• Bump the underlying PHP SDK to version ^3.19 (#725)

4.8.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.8.0.

Features

• Set cache keys as span descriptions (#677)

  To better identify the source of a cache operation, we now set the cache key as the description of cache op spans.

Bug Fixes

• Add direct dependency for guzzlehttp/psr7 (#708)
• Drop kernel.build_dir param below Symfony 5.2 (#711)

4.7.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.7.0.

Features

• Add profiles_sample_rate config option (#698)

  With this new config option, you can now use our new profiling feature in Symfony as well.
  Please consult https://github.com/getsentry/sentry-php/releases/3.15.0 for setup instructions.

4.6.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.6.0.
This release contains a colorful bouquet of new features.

Features

• Report exceptions to Sentry as unhandled by default (#674)

  All unhandled exceptions will now be marked as handled: false. You can query for such events on the issues list page,
  by searching for error.handled:false.

• Exceptions from messages which will be retried are sent to Sentry as handled (#674)

  All unhandled exceptions happening on the message bus will now be unpacked and reported individually.
  The WorkerMessageFailedEvent::willRetry property is used to determine the handled value of the event sent to Sentry.

• Add register_error_handler config option (#687)

  With this option, you can disable the global error and exception handlers of the base PHP SDK.
  If disabled, only events logged by Monolog will be sent to Sentry.

    sentry:
        dsn: '%env(SENTRY_DSN)%'
        register_error_listener: false
        register_error_handler: false
  
    monolog:
        handlers:
            sentry:
                type: sentry
                level: !php/const Monolog\Logger::ERROR
                hub_id: Sentry\State\HubInterface

• Add before_send_transaction (#691)

  Similar to before_send, you can now apply additional logic for transaction events.
  You can mutate the transaction event before it is sent to Sentry. If your callback returns null,
  the event is dropped.

    sentry:
        options:
            before_send_transaction: 'sentry.callback.before_send_transaction'
  
    services:
        sentry.callback.before_send_transaction:
            class: 'App\Service\Sentry'
            factory: [ '@App\Service\Sentry', 'getBeforeSendTransaction' ]

    <?php
  
    namespace App\Service;
  
    class Sentry
    {
        public function getBeforeSendTransaction(): callable
        {
            return function (\Sentry\Event $event): ?\Sentry\Event {
                return $event;
            };
        }
    }

• Use the _route attribute as the transaction name (#692)

  If you're using named routes, the SDK will default to use this attribute as the transaction name.
  With this change, you should be able to see a full list of your transactions on the performance page,
  instead of << unparameterized >>.

  You may need to update your starred transactions as well as your dashboards due to this change.

Bug Fixes

• Sanatize HTTP client spans (#690)

4.5.0

• Symfony version 3.4 is no longer supported
  • Drop Symfony support below 4.4 (#643)
• feat: Add support for tracing of Symfony HTTP client requests (#606)
  • feat: Add support for HTTP client baggage propagation (#663)
  • ref: Add proper HTTP client span descriptions (#680)
• feat: Support logging the impersonator user, if any (#647)
• ref: Use a constant for the SDK version (#662)

4.4.0

• feat: Add support for Dynamic Sampling (#665)

4.3.1

fix: Update span ops (#655)

4.3.0

• Fix compatibility issue with Symfony >= 6.1.0 (#635)
• Add TracingDriverConnectionInterface::getNativeConnection() method to get the original driver connection (#597)
• Add options.http_timeout and options.http_connect_timeout configuration options (#593)