Releases: getsentry/sentry-laravel
Releases · getsentry/sentry-laravel
2.5.1
- Fix problem with queue tracing when triggered from unit tests or when missing a queue name in the event
2.5.0
- Add
sql.origin
to SQL query spans with the file and line where the SQL query originated from (#398) - Remove wrapper around the context of log entry breadcrumbs (#405)
- Ensure user integrations are always executed after SDK integrations (#474)
- Fix repeated booted callback registration from performance tracing middleware (#475)
- Add tracing support for queue jobs, enable with
SENTRY_TRACE_QUEUE_ENABLED=true
(#478) - Add options to disable parts of performance tracing (#478)
- Remove string representation of exception from exceptions logged through log channels (#482)
- Use message from Monolog record to prevent bloating the log message being recorded with timestamps and log log level (#482)
- Add
report_exceptions
option to the Sentry log channel that can be set tofalse
to not report exceptions (#482)
2.4.2
2.4.1
2.4.0
- Read the request IP from the Laravel request to make it more accurate when behind a reverse proxy (requires trusted proxies to be setup correctly) (#419)
- Get request information (like the URL) from the Laravel request instead of constructing it from the global state (#419)
- Fix generated route name not correctly ignored when using prefix (#441)
- Fix overwriting the transaction name if it's set by the user (#442)
- Add result from optional
context(): array
method on captured exception to the event sent to Sentry (#457) - Fix not overwriting the event transaction name if it was an empty string (#460)
- Bump Sentry SDK to
3.2.*