4.6.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.6.1.

Bug Fixes

• Fix wrong queue grouping in the queue Insights Module (#910)

4.6.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.6.0.

Features

• Add support for the Queue Insights Module (#902). To learn more about this module, visit https://docs.sentry.io/product/performance/queue-monitoring/.

  Queue tracing is enabled by default for new SDK installations. To enable this feature in your existing installation, update your config/sentry.php file with 'queue_jobs' => env('SENTRY_TRACE_QUEUE_JOBS_ENABLED', true), or set SENTRY_TRACE_QUEUE_JOBS_ENABLED=true in your environment (#903).

Bug Fixes

• Check if a span is sampled before creating child spans (#898)

• Always register the console sentryMonitor() macro. This fixes the macro not being available when using Laravel Lumen (#900)

• Avoid manipulating the config when resolving disks (#901)

Misc

• Various Spotlight improvements, such as the addition of a new SENTRY_SPOTLIGHT environment variable and not requiring a DSN to be set to use Spotlight (#892)

4.5.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.5.1.

Bug Fixes

• Fix discarded attribute violation reporter not accepting multiple property names (#890)

4.5.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.5.0.

Features

• Limit when SQL query origins are being captured (#881)

  We now only capture the origin of a SQL query when the query is slower than 100ms, configurable by the SENTRY_TRACE_SQL_ORIGIN_THRESHOLD_MS environment variable.

• Add tracing and breadcrumbs for Notifications (#852)

• Add reporter for Model::preventAccessingMissingAttributes() (#824)

• Make it easier to enable the debug logger (#880)

  You can now enable the debug logger by adding the following to your config/sentry.php file:

  'logger' => Sentry\Logger\DebugFileLogger::class, // This will log SDK logs to `storage_path('logs/sentry.log')`

  Only use this in development and testing environments, as it can generate a lot of logs.

Bug Fixes

• Fix Lighthouse operation not detected when query contained a fragment before the operation (#883)

• Fix an exception being thrown when the username extracted from the authenticated user model is not a string (#887)

4.4.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.4.1.

Bug Fixes

• Fix assertExists/assertMissing can throw on the FilesystemDecorator (#877)

4.4.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.4.0.

Features

• Add support for Laravel 11 Context (#869)

  If you are using Laravel 11 and the new "Context" capabilities we now automatically capture that context for you and it will be visible in Sentry.
  Read more about the feature in the Laravel documentation and how to use it.

4.3.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.3.1.

Bug Fixes

• Add missing methods to FilesystemDecorator (#865)

4.3.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.3.0.

Features

• Add support for Laravel 11.0 (#845)

  If you're upgrading an existing Laravel 10 application to the new Laravel 11 directory structure, you must change how Sentry integrates into the exception handler. Update your bootstrap/app.php with:

  <?php
  
  use Illuminate\Foundation\Application;
  use Illuminate\Foundation\Configuration\Exceptions;
  use Illuminate\Foundation\Configuration\Middleware;
  use Sentry\Laravel\Integration;
  
  return Application::configure(basePath: dirname(__DIR__))
      ->withRouting(
          web: __DIR__.'/../routes/web.php',
          commands: __DIR__.'/../routes/console.php',
          health: '/up',
      )
      ->withMiddleware(function (Middleware $middleware) {
          //
      })
      ->withExceptions(function (Exceptions $exceptions) {
          Integration::handles($exceptions);
      })->create();

  If you plan to perform up-time checks against the new Laravel 11 /up health URL, ignore this transaction in your config/sentry.php file, as not doing so could consume a substantial amount of your performance unit quota.

  // @see: https://docs.sentry.io/platforms/php/guides/laravel/configuration/options/#ignore-transactions
  'ignore_transactions' => [
      // Ignore Laravel's default health URL
      '/up',
  ],

Bug Fixes

• Set queue.publish spans as the parent of queue.process spans (#850)

• Consider all http_* SDK options from the Laravel client in the test command (#859)

4.2.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.2.0.

Features

• Add new spans, measuring the time taken to queue a job (#833)

• Add support for failure_issue_threshold & recovery_threshold for sentryMonitor() method on scheduled commands (#838)

• Automatically flush metrics when the application terminates (#841)

• Add support for the W3C traceparent header (#834)

• Improve php artisan sentry:test to show internal log messages by default (#842)

4.1.2

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.1.2.

Bug Fixes

• Fix unable to set callable for integrations option (#826)

• Fix performance traces not being collected for Laravel Lumen unless missing routes are reported (#822)

• Fix configuration options for queue job tracing not applying correctly (#820)

Misc

• Allow newer versions of symfony/psr-http-message-bridge dependency (#829)