The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.9.2.
We decided to revert two previous PRs that aimed to remove deprecation warnings during test runs (#736)
We are sorry for the inconvenience caused by these changes.
The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.9.1.
TracingDriverForV32 by adding VersionAwarePlatformDriver::createDatabasePlatformForVersion (#731)The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.9.0.
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.
http_connect_timeoutand http_timeout options (#721)^3.19 (#725)The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.8.0.
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.
The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.7.0.
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.
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.
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](https://github.com/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.
>= 6.1.0 (#635)TracingDriverConnectionInterface::getNativeConnection() method to get the original driver connection (#597)options.http_timeout and options.http_connect_timeout configuration options (#593)PDOStatement::bindParam() method and passing $length = null on DBAL 2.x (#613)>= 2.6.0 (#608)PDOStatement::bindParam() method and passing $length = null (#586)symfony/cache-contracts package version 3.x (#588)3.4 (#570)SentryExtension class to prepare for Symfony 6 (#563)TracingDriverConnection::errorCode() (#568)ServerInfoAwareConnection interface (#567)TracingStatement exists before attempting to create the class alias, otherwise it breaks when opcache is enabled. (#552)logger config option to TransportFactory (#555)Statement::execute() method of Doctrine DBAL (#548)TracingDriver::getDatabase() method (#541)TraceableCacheAdapterTrait::prune() and TraceableCacheAdapterTrait::reset() methods when the decorated adapter does not implement the respective interfaces (#543)sentry_trace_meta() Twig function to print the sentry-trace HTML meta tag (#510)TracingDriverConnection::getWrappedConnection() (#536)logger config option to ease setting a PSR-3 logger to debug the SDK (#538)^2.13|^3; simplify the DBAL tracing feature (#527)The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.13.2.
symfony/http-client (#797)The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.13.1.
http_client service is registered (#792)The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v4.10.0.
Tracing without Performance (#742)
The SDK will now continue a trace from incoming HTTP requests, even if performance is not enabled. To continue a trace outward, you may attach the Sentry tracing headers to any HTTP client request. You can fetch the required header values by calling \Sentry\getBaggage() and \Sentry\getTraceparent().
Add ignore_exceptions and ignore_transactions options (#724)
5.3 (#518)symfony/cache-contracts package (#506)CacheItem class while attempting to enable the cache instrumentation (#501)5.3 (#489)SERVER_PROTOCOL header is missing (#495)RequestFetcher fails to translate the Request (#472)Sentry\SentryBundle\EventListener\ConsoleCommandListener class in favor of its parent class Sentry\SentryBundle\EventListener\ConsoleListener (#429)symfony/psr-http-message-bridge to allow installing it on a project that uses Symfony 3.4.x components only (#480)null value on DSN not disabling Sentry (#457)kernel.project_dir to prefixes default value to trim paths to the project root (#434)null, false or empty value not disabling Sentry (#454)capture-soft-fails option to the XSD schema for the XML config (#417)send_default_pii option is off (#425)register_error_listener option is disabled (#427)Breaking Change: This version uses the envelope endpoint. If you are
using an on-premise installation it requires Sentry version >= v20.6.0 to work. If you are using
sentry.io nothing will change and no action is needed.
options.traces_sampler and options.traces_sample_rate configuration options (#385)options.project_root configuration option. Instead of setting it, use a combination of options.in_app_include and options.in_app_exclude (#385)options.excluded_exceptions configuration option. Instead of setting it, configure the IgnoreErrorsIntegration integration (#385)ConsoleCommandListener, ErrorListener, RequestListener and SubRequestListener event listeners (#387)RequestStack when using the RequestIntegration integration (#361)monolog configuration option. Instead, register the service manually (#406)listener_priorities configuration option. Instead, use a compiler pass to change the priority of the listeners (#407)Symfony\Bridge\PsrHttpMessage\HttpMessageFactoryInterface service for the RequestFetcher class (#409)RequestListener and SubRequestListener listeners (#414)jean85/pretty-package-versions ^1.5 to leverage the new getRootPackageVersion method (c8799ac)capture_soft_fails: false option for the Messenger (#353)release option default value (#325)in_app_include to empty, due to getsentry/sentry-php#958 (#311)class_alias (#313)class_alias to fix deprecations, which could break BC layers of third party packages (#309, thanks to @scheb)sentry/sentry 2.3 (#298)sentry/sentry < 2.3 (#298)in_app_include client option (#298)excluded_exceptions option to use the new IgnoreErrorsIntegration (#298)release option, using the detected root package version (#291 #292, thanks to @Ocramius)ConsoleListener (#261)RequestListener (#264)RequestListener (#263)ErrorListener (#243, thanks to @teohhanhui)class_serializers option (#245)max_request_body_size option (#249)The 3.0 major release has multiple breaking changes. The most notable one is the upgrade to the 2.0 base SDK client. Refer to the UPGRADE-3.0.md document for a detailed explanation.
sentry:test command, to test if the Sentry SDK is functioning properly.How can I help you explore Laravel packages today?