Pretty good article. ~/blainsmith you can increase the counter of Go devs that didn't know about httptrace. :D I'm mildly ashamed, but on the other hand I've never worked in code bases where tracing information was meaningful at that level. :D
I also wasn't aware of net/http/httptrace before reading this article. Now I can start removing a bunch of http.RoundTrippers that I implemented for capturing request durations...
I learned a lot of this at my time with https://subspace.com when I was on the telemetry team responsible for tracing the network to inform pathfinding. It was a very niche role that launched my interest in low-level network projects where I found my true passion.
blainsmith | a day ago
Author here... Thanks for sharing this. It has been fun to use while we get ready to launch https://probes.dev with tracing being core to the service.
mariusor | a day ago
I've seen your posts about it on mastodon, but I wasn't aware it's something you're involved with on a fundamental level. Congrats on the launch.
blainsmith | a day ago
Cool. Yeah, it is my brain child idea that I started from scratch that is very close!
mariusor | a day ago
Pretty good article. ~/blainsmith you can increase the counter of Go devs that didn't know about httptrace. :D I'm mildly ashamed, but on the other hand I've never worked in code bases where tracing information was meaningful at that level. :D
[OP] klingtnet | a day ago
I also wasn't aware of
net/http/httptracebefore reading this article. Now I can start removing a bunch ofhttp.RoundTrippers that I implemented for capturing request durations...blainsmith | a day ago
I learned a lot of this at my time with https://subspace.com when I was on the telemetry team responsible for tracing the network to inform pathfinding. It was a very niche role that launched my interest in low-level network projects where I found my true passion.