Interceptors that ensure observatility information is sent to X-Ray
TODO: Document the XRayInterceptor
🎉 Sparta v1.7.0: The Time Machine Edition 🕰 🎉
— Matt Weagle (@mweagle) November 12, 2018
For those times when you wish you could go back in time and enable debug logging for a single request.https://t.co/BP60qQpKva#serverless #go
Sparta v1.7.0 adds `Interceptors`: user defined hooks called during the lambda event handling flow to support cross-cutting concerns. The first interceptor is an XRay annotation and metadata interceptor. https://t.co/HaxPd6P4KE
— Matt Weagle (@mweagle) November 12, 2018
☢️ The XRayInterceptor works with your existing logging calls and can optionally publish ring-buffered log messages to the XRay segment *only if* there was an error. No error, no worries. ☢️https://t.co/bqp8MXiCHt
— Matt Weagle (@mweagle) November 12, 2018
In case of an error, visit the Trace in the XRay console and dig into a state-preserving representation of the request, including the AWS Request ID. Your log statement can publish a PII-aware redacted event. pic.twitter.com/Tm5aFgUhcc
— Matt Weagle (@mweagle) November 12, 2018
An opportunity to make your Future-3am-Self much more rested in fewer than 6 lines of code. https://t.co/Y7D5rBM0k7 pic.twitter.com/zv3JQWi41P
— Matt Weagle (@mweagle) November 12, 2018
Last thing - you can also enable BuildID segment annotation so that you can use XRay filter expressions. Navigate your service's evolution and failure profile over time.
— Matt Weagle (@mweagle) November 12, 2018
First rule of debug club: what's running?
Pencils down until re:Invent...https://t.co/EtazcpzYTT
Shout out to https://t.co/om0ljHBfDe for guidance.
— Matt Weagle (@mweagle) November 12, 2018