Thanks for stopping by to let us know something could be better!

Is your feature request related to a problem? Please describe.
When reviewing traces from my application, I only see the high-level operation of the client. Beyond that, the operation of the client library (e.g. requests made, backoff and retries) are not present in tracing data.

I would like to see detailed spans (in tracing) for each individual HTTP request that is sent from the client. These traces should ultimately have details like the ones defined by Open Telemetry HTTP semantic conventions (e.g. method, service name and port.)

Describe the solution you'd like

Describe alternatives you've considered

Additional context