Implement support for httptrace debugging feature

[remyleone]

Description

As a plugin developer, I would like to have support for sending httptrace debugging information.
As a first step, printing the different steps of the HTTP transaction could be a good start to help plugin developpers.
As a second step, those logs could be sent to a dedicated log service (but that seems overkill for the first iteration).
This could leave inside the communicator code (plugin-sdk).

Use Case(s)

This could be useful to see if an HTTP request gets stuck where it is stuck exactly.

Potential References

• https://www.youtube.com/watch?v=u3YWN4TF81w

[azr]

Hey @remyleone, thanks for opening !
Just to clarify, that httptrace debugging information, you would like to print it for debugging purpose ? Or, send it somewhere?

[remyleone]

Updated :) as a first step, printing it is fine. The main goal is to identify problems like slow DNS resolution or retries that are too numerous.

[azr]

Gotcha ! Yeah, I think this would be a good idea; we could propose a http package in the SDK that gives a function that returns a httptrace.ClientTrace{.