You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A temporary workaround is to change the configuration in `sentry.php
// Performance monitoring specific configuration'tracing' => [
// Configures if the performance trace should continue after the response has been sent to the user until the application terminates// This is required to capture any spans that are created after the response has been sent like queue jobs dispatched using `dispatch(...)->afterResponse()` for example'continue_after_response' => env('SENTRY_TRACE_CONTINUE_AFTER_RESPONSE', false),
],
Do we need to update Lumen's documentation to avoid errors for others.? Or there are more elegant ways to deal with it
The text was updated successfully, but these errors were encountered:
How do you use Sentry?
Self-hosted / on-premises
SDK version
4.1
Steps to reproduce
When I use
tracing
to report data I get this error.I use
lumen
.lumen
version isv8.2.3
vendor/sentry/sentry-laravel/src/Sentry/Laravel/Tracing/Middleware.php
I found that
lumen
version 9.x has this method. https://github.com/laravel/lumen-framework/blob/9.x/src/Application.phpA temporary workaround is to change the configuration in `sentry.php
Do we need to update Lumen's documentation to avoid errors for others.? Or there are more elegant ways to deal with it
The text was updated successfully, but these errors were encountered: