Client Tracing

[hynek]

Go 1.7 added tracing to its http client which I find quite intriguing:

The collected information can be used for debugging latency issues, service monitoring, writing adaptive systems, and more.

HTTP events

The httptrace package provides a number of hooks to gather information during an HTTP round trip about a variety of events. These events include:

• Connection creation
• Connection reuse
• DNS lookups
• Writing the request to the wire
• Reading the response

Is that something you’d find a good fit for aiohttp?

[asvetlov]

Brilliant idea.
Perhaps aiohttp signals could be reused for hooks implementation

[thehesiod]

btw in a sorta related note I'm adding this to DataDog in this PR: DataDog/dd-trace-py#294

[asvetlov]

If you want to pick up the issue (very complex task btw but we can eat an Elephant piece by piece) you are welcome.
It could not only avoid patching aiohttp code by DataDog but is very useful for other aiohttp users.

[asvetlov]

Close for sake of #2313

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs.
If you feel like there's important points made in this discussion, please include those exceprts into that [new issue].
[new issue]: https://github.com/aio-libs/aiohttp/issues/new