Trent Mick
Trent Mick
@elasticmachine, run elasticsearch-ci/docs
The "test all versions" tests failed on the `captureBody` test with fastify@1 and node@10. For some reason that I didn't dig into, the `preHandler` life-cycle hook doesn't run with fastify@1...
@elasticmachine, run elasticsearch-ci/docs
run module tests for fastify
Hi @alexsanderp. Thanks for the issue. (I don't use winston much myself, so it took me a little while before I realized that winston has an `uncaughtException` handler by default....
From playing a little bit, the HTTP response has ended (and the APM instrumentation of core http has ended the transaction) before hapi sends the 'response' event. I think it...
To answer the question posed by the issue title: **No**, the APM transaction for the request/response being reported in the hapi 'response' event is not the "apm.currentTransaction" in the response...
I'm re-opening for discussion on improving our Hapi instrumentation and to get on planning radar.
> We can work the problem around on the Kibana level. What if I store `trace.id` during `onPreResponse` and use it later? Yes, that sounds reasonable. It is nice that...
> However, using the `onPreResponse` lifecycle for `response` logging can lead to hard-to-debug problems. > ... That block is a very good argument for binding the APM transaction to the...