X-Ray Integration Changelog
1.10.0
August 8, 2026
Add the Route annotation on the root trace (not just the Routing segment), that will allow searching/filtering.
1.9.0
July 27, 2026
- Guzzle 8 support: the library now works with both Guzzle 7 and Guzzle 8 (
guzzlehttp/guzzle: ^7 | ^8).
- Failed HTTP requests made with Guzzle are now highlighted in the X-Ray console: HTTP calls that return a 4xx response are flagged as errors, and 5xx responses as faults, like with the official X-Ray SDKs.
- Honor
AWS_XRAY_SDK_ENABLED=false: you can now disable tracing entirely by setting this environment variable (the same one used by the official X-Ray SDKs), useful for example in dev/testing environments.1.8.0
May 7, 2026
Enrich AWS SDK segments
1.7.8
April 9, 2026
Ignore the second Response event from Laravel.
1.7.7
April 8, 2026
Add a new Response segment for Laravel apps.
1.7.6
March 16, 2026
Actually allow Symfony 8 :)
1.7.5
March 16, 2026
Allow Symfony 8
1.7.4
February 26, 2026
Allow Laravel 13.
1.7.3
October 24, 2025
Add support for Bref v3 beta versions.
1.7.2
October 14, 2025
Fix support for Laravel 10.
1.7.1
September 24, 2025
Fix type issues.
1.7.0
September 8, 2025
Trace the Laravel HTTP client automatically.
1.6.5
May 7, 2025
Improve the Xray::subSegment() low-level API.
1.6.4
April 9, 2025
What's Changed
* Improve Symfony declared services by @mnapoli in https://github.com/brefphp/xray-integration/pull/10
1.6.3
April 8, 2025
Solve type error with null trace ID.
1.6.2
April 8, 2025
Autoregister GuzzleTracer for Symfony.
1.6.1
April 2, 2025
What's Changed
* Automatically trace Laravel Queues requests to SQS by @mnapoli in https://github.com/brefphp/xray-integration/pull/8
1.6.0
March 31, 2025
Symfony support
1.5.0
March 24, 2025
Use Bref's cold start tracking mechanism
1.4.0
March 11, 2025
- Added
XRay::subSegment()