Releases: getsentry/sentry-laravel
4.15.0
The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.15.0.
Features
-
Add support for Sentry Structured Logs (#1000)
To enable this feature, add the
sentry_logs
log channel in yourconfig/logging.php
configuration:'channels' => [ ... 'sentry' => [ 'driver' => 'sentry_logs', 'level' => env('LOG_LEVEL', 'info'), ], ... ],
Add
SENTRY_ENABLE_LOGS=true
to your.env
file.Use the Log facade to sent your logs to Sentry. To learn more, head over to the Laravel docs.
use Illuminate\Support\Facades\Log; Log::driver('sentry')->info('User {id} failed to login.', ['id' => $user->id]);
4.14.1
The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.14.1.
Bug Fixes
-
Ensure there is a newline before writing env variables (#1002)
Fixed an issue where the
php artisan sentry:publish
command might not properly add newlines when writing environment variables to the.env
file.
4.14.0
Bug Fixes
-
Fix tracing when using Laravel Octane (#997)
When using Laravel Octane, the SDK now correctly cleans up it's state after each request, ensuring that traces are correctly reported.
Misc
-
Add
sentry
prefix to publish group name (#992)When running
php artisan vendor:publish
, the Sentry package exports are now prefixed withsentry
, making it easier to distinguish from other packages. -
Remove support for
traceparent
header (#994)The W3C's
traceparent
header is no longer automatically picked up and emitted by the SDK to prevent non-Sentry SDKs from starting a trace that is unwanted.
4.13.0
4.12.0
The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.12.0.
Features
-
Improve generation of slug for scheduled job cron monitoring (#977)
For scheduled jobs it's no longer needed to manually provide a slug to the
->sentryMonitor()
call, it will be derived from the job class name.
Bug Fixes
Misc
-
Disable scheduled task tracing for backgrounded tasks (#975)
Backgrounded tasks show up a ~1ms transactions right now because we are effectively monitoring the time it takes to start the background process instead of the execution.
We are working on a solution to this problem, but in the meantime, we are disabling the monitoring of backgrounded tasks (that was introduces in 4.11.0).