Releases: getsentry/sentry-php
Releases · getsentry/sentry-php
3.13.0
The Sentry SDK team is happy to announce the immediate availability of Sentry PHP SDK v3.13.0.
Features
-
Object IDs are now automatically serialized as part of a stack trace frame (#1443)
- If
Obj::getID()
orObj->id
is accessible, this value will be displayed inside the stack trace frame on the issue details page.
To attach local variables to your stack trace, make surezend.exception_ignore_arg: 0
is set in yourphp.ini
.
See https://docs.sentry.io/platforms/php/troubleshooting/#missing-variables-in-stack-traces
- If
-
Add more functionality to the
ExceptionMechanism::class
(#1450)- Attach arbitrary data
Learn more about the interface of the
$hint = EventHint::fromArray([ 'exception' => $exception, 'mechanism' => new ExceptionMechanism( ExceptionMechanism::TYPE_GENERIC, false, [ 'key' => 'value', //... ], ), ]); captureEvent(Event::createEvent(), $hint);
ExceptionMechanism
on https://develop.sentry.dev/sdk/event-payloads/exception/#exception-mechanism - Access or mutate
ExceptionMechanism::data
viaExceptionMechanism::getData()
andExceptionMechanism::setData()
- If an exception contains a user-provided
code
, the value will be serialized into the event and displayed on the issues details page.throw new \Exception('Oh no!', 123);
- Attach arbitrary data
3.12.1
3.12.0
3.11.0
3.10.0
3.9.1
3.9.0
- feat: Add tracePropagationTargets option (#1396)
- feat: Expose a function to retrieve the URL of the CSP endpoint (#1378)
- feat: Add support for Dynamic Sampling (#1360)
- Add
segment
toUserDataBag
- Add
TransactionSource
, to set information about the transaction name viaTransactionContext::setSource()
(#1382) - Deprecate
TransactionContext::fromSentryTrace()
in favor ofTransactionContext::fromHeaders()
- Add