There 's a few tickets in the Laravel repositories, but it looks like the reason is an upgrade of the Sentry library to 1.0

Basically we all see ErrorException Warning: PDO::prepare(): MySQL server has gone away reports in Sentry, while it supposed to be caught by Laravel, and handle it.

But since the 1.0 update of Sentry library, it somehow bubbles up :)

https://github.com/laravel/horizon/issues/583 https://github.com/laravel/framework/issues/28920

Hi,

I can't install the package through composer.

Here is the error:

  Problem 1
    - Installation request for sentry/sentry-laravel ^1.0 -> satisfiable by sentry/sentry-laravel[1.0.0, 1.0.0-beta1, 1.0.0-beta2, 1.0.0-beta3, 1.0.0-beta4, 1.0.0-beta5, 1.0.1, 1.0.x-dev].
    - Can only install one of: php-http/httplug[v2.0.0, v1.1.0].
    - Can only install one of: php-http/httplug[v1.1.0, v2.0.0].
    - Can only install one of: php-http/httplug[v1.1.0, v2.0.0].
    - Conclusion: install php-http/httplug v1.1.0
    - Installation request for php-http/httplug (locked at v2.0.0) -> satisfiable by php-http/httplug[v2.0.0].

Hi,

After updating to 2.0.1, we get those errors : Call to undefined method Sentry\Tracing\Transaction::setHttpStatus()' in src/Sentry/Laravel/Tracing/Middleware.php:66

Looks like the Transaction::setHttpStatus() is quite new and has been introduce in the SDK on version 3.0.2 with this PR: https://github.com/getsentry/sentry-php/pull/1092

The thing is, the composer.json file in the 2.0.1 release mention this requirement: "sentry/sdk": "^3.0".

You probably should force the version of "sentry/sdk" to at least 3.0.2 in order not to break your tracing middleware.

When I run the app('sentry')->captureException($error); , the speed of the program is very slow. i think you need to job in laravel or lumen.But this has many problems، for example: exception can not be serialize

Ever since upgrading from 1.0.0-beta2 to 1.1.0 I am sometimes seeing two issues for a single exception, one prefaced with Notice:. This was one I created:

This could be happening every time, but I'm not sure as I am 2 days from launch. Is this from upgrading or something on my end?

At the time of upgrade I also stopped receiving emails for Laravel issues (but still get JS emails). I have checked my settings (that I didn't ever change) and they look correct to alert me. Anyone else?

Having issues with release tracking

https://stackoverflow.com/questions/65066899/release-tracking-an-error-doesnt-associate-to-a-recent-release

I have added tag to the middleware for sentry and laravel.

$scope->setTag('release', trim(exec('git ' . base_path('.git-ftp.log') . ' log --pretty="%h" -n1 HEAD')) ? : 'No Valid Tag?' ); but it wont associate a tag, even with a static typed value matching to a old commit hash that sentry sees in the releases menu

See https://docs.sentry.io/platforms/php/guides/laravel/enriching-events/scopes/

I believe theres an issue with the SDK.

I have tested and confirmed that I can verify the commit hash are both current, and matching

Please Message me on Sentry Discord under user Levi Z

Installation

Read https://docs.sentry.io/performance-monitoring/performance/ to understand the concept behind Tracing/Performance in Sentry.

Make sure you have following in you composer.json

"require": {
        "sentry/sentry-laravel": "dev-performance/beta"
},
"minimum-stability": "dev",
"prefer-stable": true,

After that run composer update.

Make sure the installation of sentry/sentry, sentry/sdk and sentry/sentry-laravel in the output looks something like this:

 - Installing sentry/sentry (3.x-dev dd6ef34)
 - Installing sentry/sdk (3.x-dev f6b434e)
 - Installing sentry/sentry-laravel (dev-performance/beta 745bd72)

The important part is that both sentry/sentry and sentry/sdk are 3.x where sentry/sentry-laravel is dev-performance/beta.

After that add 'traces_sample_rate' => 1.0, to the file in config/sentry.php. Note that the value should be larger than 0.0 and smaller or equal than 1.0 (to send everything). More info can be found here: https://docs.sentry.io/performance-monitoring/getting-started/

Connecting your frontend

To setup tracing for your Vue frontend, follow: https://docs.sentry.io/performance-monitoring/getting-started/?platform=vue

An additional step you should take is, add this to your blade template rendering the <head> tag {!! Sentry\Laravel\Integration::sentryTracingMeta() !!} This adds a meta tag similar to <meta name="sentry-trace" content="ae02a316231d490c870b14f27aba8d29-c4a72ffd39444c84-1"/> to your header and tells the frontend code to pick up the trace.

Known Issues

• Right now we are not using an agent to send those transactions meaning Laravel sends the Transactions after finishing serving the request but the process is only terminated once the Transaction is sent. It shouldn't impact your users a lot but something to keep in mind.
• If you are using on-premise you need to make sure to use the latest release of Sentry https://github.com/getsentry/sentry/releases/tag/20.6.0 or master. Transactions hit a new endpoint and can only be received there.

Papertrail

• [x] Record sql queries as spans
• [x] Record rendered views as spans
• [x] Get route name like /users/{id} instead of /users/1
• [x] Start Transaction from incoming headers
• [ ] Collect query span regardless of sentry.breadcrumbs.sql_queries option?

This works together with https://github.com/getsentry/sentry-php/pull/1031

Resulting in:

I recenty got this error after upgrading our composer. Did the original Sentry package got updated where the Raven_Client got deprecated or so?

PHP Fatal error: Uncaught Error: Class 'Raven_Client' not found in /api/vendor/sentry/sentry-laravel/src/Sentry/SentryLaravel/SentryLaravel.php:18 Stack trace: #0 /api/vendor/sentry/sentry-laravel/src/Sentry/SentryLaravel/SentryLaravelServiceProvider.php(101): Sentry\SentryLaravel\SentryLaravel::getClient(Array) #1 /api/vendor/laravel/framework/src/Illuminate/Container/Container.php(776): Sentry\SentryLaravel\SentryLaravelServiceProvider->Sentry\SentryLaravel\{closure}(Object(Illuminate\Foundation\Application), Array) #2 /api/vendor/laravel/framework/src/Illuminate/Container/Container.php(658): Illuminate\Container\Container->build(Object(Closure)) #3 /api/vendor/laravel/framework/src/Illuminate/Container/Container.php(609): Illuminate\Container\Container->resolve('sentry', Array) #4 /api/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(759): Illuminate\Container\Container->make('sentry', Array) #5 /api/vendor/sentry/sentry-laravel/src/Sentry/SentryLaravel/SentryLaravel.php on line 18

I'm trying to install Sentry on a Laravel 5 project but I'm already using Cartalyst Sentry for user authentication - which has an existing facade for "sentry." Is there a workaround for this?

Environment

How do you use Sentry? Sentry SaaS (sentry.io)

Which SDK and version? composer require sentry/sentry-laravel Laravel v7.30.6 PHP 7.4.27

Steps to Reproduce

Just in command line: composer require sentry/sentry-laravel

Expected Result

Sentry installed successfully

Actual Result

Illuminate\Foundation\ComposerScripts::postAutoloadDump
@php artisan package:discover --ansi

   Illuminate\Contracts\Container\BindingResolutionException 

  Target class [hash] does not exist.

  at vendor/laravel/framework/src/Illuminate/Container/Container.php:811
    807| 
    808|         try {
    809|             $reflector = new ReflectionClass($concrete);
    810|         } catch (ReflectionException $e) {
    811|             throw new BindingResolutionException("Target class [$concrete] does not exist.", 0, $e);
    812|         }
    813| 
    814|         // If the type is not instantiable, the developer is attempting to resolve
    815|         // an abstract type such as an Interface or Abstract Class and there is

      34 vendor frames 
  35  app/Console/Kernel.php:186
      Illuminate\Foundation\Console\Kernel::bootstrap()

      1 vendor frames 
  37  artisan:37
      Illuminate\Foundation\Console\Kernel::handle()

Environment

Ubuntu 20.04 with stock Composer 1, PHP 7.4

How do you use Sentry?

self-hosted/on-premise for a Laravel app using sentry-laravel

Steps to Reproduce

Our installs are currently blocked due to composer throwing this error since 24 May 2021. When running any composer command such as dump-autoload, install or update, it currently generates an error:

$ sg www-data 'composer dump-autoload' Generating optimized autoload files composer/package-versions-deprecated: Generating version class... composer/package-versions-deprecated: ...done generating version class

Illuminate\Foundation\ComposerScripts::postAutoloadDump @php artisan package:discover --ansi

OutOfBoundsException

Package "sentry/sentry" is not installed

at vendor/composer/composer/src/Composer/InstalledVersions.php:166 162▕ 163▕ return $installed['versions'][$packageName]['pretty_version']; 164▕ } 165▕ ➜ 166▕ throw new \OutOfBoundsException('Package "' . $packageName . '" is not installed'); 167▕ } 168▕ 169▕ /** 170▕ * @param string $packageName

  +17 vendor frames 

18 app/Exceptions/Handler.php:47 app()

  +2 vendor frames 

21 [internal]:0 Illuminate\Foundation\Bootstrap\HandleExceptions::handleException() Generated optimized autoload files containing 11178 classes

There are indications this is a bug in one or a combinations of the following components:

laravel-sentry
composer (particularly version 1 vs 2)
phpstan
ocramius/package-versions or whichever variant we have

Similar threads:

https://github.com/getsentry/sentry-laravel/issues/274 https://github.com/getsentry/sentry-symfony/issues/383

Sentry has a (in beta since forever) CRON monitoring: https://docs.sentry.io/product/crons/.

It would be really sweet if we can somehow automatically set that up for the user based on their scheduled tasks (basically CRONs): https://laravel.com/docs/9.x/scheduling#defining-schedules.

I'm imagining this requires some sort of synchronize command to be run to talk with Sentry and create the correct CRONs on the Sentry server so depending on how this actually works this might be very easy or tricky or out of scope for the SDK. Will require some investigation but it's an interesting idea!

As requested by @ankurk91: https://github.com/getsentry/sentry-laravel/issues/625#issuecomment-1362767006.

With the Illuminate\Redis\Events\CommandExecuted we could add spans for redis commands. We do this in the Symfony SDK where cache calls are profiled, maybe we could generelize since just Redis spans don't seem too interesting but cache performance spans could ne nice to see since they do take time but haven't looked to close if there are command where we can hook into the cache events.

The Laravel gates feature allow us to define callbacks with Gate::before and Gate::after, we could use this to create a span for the gate check (since gates might execute queries) and add breadcrumbs that a gate authorization has taken place. This could be interesting data to see back in the performance traces and make it easier to find where queries are coming from + the breadcrumbs might be interesting too especially if we can add some information on what gate and gate method was called and mabe even what the result was.

We could listen to the Illuminate\Mail\Events\MessageSending and Illuminate\Mail\Events\MessageSent events to figure out when an mail was sent and possibly nest the view rendering needed to sent that e-mail neatly underneath a mail span.

We could potentially also add a breadcrumb indicating an email was sent by the framework.

The same goes for notifications (which could trigger e-mails) with Illuminate\Notifications\Events\NotificationSending and Illuminate\Notifications\Events\NotificationSent.

Currently when using Laravel Passport we get a big black hole in the performance spans window, making it quite hard to know what is taking the performance there.

My theory is that this is due to the nature of how Passport works underneath the hood, but it would be awesome to fill the gaps here so we can improve the performance without going completely blind in when looking at the performance :)

Adding a helper method that reduces a lot of boilerplate of adding spans for user-code to a application, allowing users to quickly wrap existing calls with a span and it looks something like this:

use Sentry\State\Scope;
use Sentry\Tracing\SpanContext;
use function Sentry\Laravel\trace;

$args = [...];

$resutl = trace(
    function (Scope $scope) use ($args) {
        $scope->setTag('some-tag', 'some-value');

        return $this->doSomethingMeasureable($args);
    },
    tap(new SpanContext, function (SpanContext $context) use ($args) {
        $context->setOp('something.measurable');
        $context->setData(['context' => $args]);
        $context->setDescription('Something measurable');
    }),
);

The SpanContext is a unfortunate object in our API at the moment and doesn't have a fluent interface so I've used the tap() helper from Laravel to keep it a little more readable.

In this exampel we also pass the current scope to the callback that is being traced, this might be a good idea or not... maybe the user should wrap this block in their own withScope but it seems easy enough to ignore if you don't want to do anything with the scope.

(this is inspired by a homegrown method I'm using in my applications to make this easier but simplified to make it more general and acceptable)

This is very much a concept and naming might probably change a lot in the process.