IdeaWell

Project ideas from Hacker News discussions.

Tracing HTTP Requests with Go's net/HTTP/httptrace

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Top Themes- Custom connection tracing

  • “I wish I had known this two years ago. I ended up writing my own embedded connection struct to trace these things.” — s-macke

  • Go’s cohesive development flow

  • “Little things like this are why Go is great. … it is about the end‑to‑end development flow.” — melodyogonna

  • Proper connection reuse and pool safety

  • “Tracking connection reuse is really important … File descriptor exhaustion happens often if you're not careful.” — Xeoncross

🚀 Project Ideas

GoConnection Tracer

Summary

  • Lightweight wrapper around net.Conn that fires custom callbacks on connection reuse, closure, and errors without pulling in heavy httptrace.
  • Solves the “I wish I had known this two years ago” pain point for Go devs tracking connection lifecycles.

Details

Key Value
Target Audience Go engineers building custom HTTP clients or middleware who need fine‑grained connection lifecycle events
Core Feature Auto‑wraps net.Conn with OnEventCallback that reports reuse, client‑close, server‑close, and error states
Tech Stack Go 1.22+, standard library net, optional sync.Pool for pooling
Difficulty Medium
Monetization Revenue-ready: SaaS tiered (Free up to 10k events/month, $0.01 per additional 1k)

Notes- Quote from HN: “I wish I had known this two years ago.”

  • Provides immediate utility for debugging connection leaks and optimizing pooling.

ConnLeak: Go HTTP Connection Leak Detector

Summary

  • CLI tool that monitors open file descriptors of Go HTTP servers/clients and alerts on potential leaks.
  • Addresses fd exhaustion worries highlighted by Xeoncross.

Details| Key | Value |

|-----|-------| | Target Audience | DevOps engineers and library authors running Go services in containers or production | | Core Feature | Scans /proc//fd and correlates with net.Conn lifecycles to flag unreleased connections | | Tech Stack | Go 1.22+, github.com/shirou/gcrypt for hashing, simple text UI (tview) | | Difficulty | Low | | Monetization | Hobby |

Notes

  • Directly useful for preventing “file descriptor exhaustion” in benchmarking scenarios.
  • Generates discussion around best practices for containerized Go services.

ConnWatch Dashboard

Summary

  • Web UI + backend service that visualizes connection reuse metrics across multiple Go services in real time.
  • Turns the abstract tracing need into an actionable dashboard.

Details

Key Value
Target Audience microservice architects and platform teams managing many Go APIs
Core Feature Aggregates event streams from Connection Tracer instances and displays reuse heatmaps, leak alerts
Tech Stack Go (gRPC server), React frontend, Redis for pub/sub
Difficulty High
Monetization Revenue-ready: Usage‑based pricing per connected service instance

Notes

  • Quoted desire: “Tracking connection reuse is really important if you are running any kind of benchmarks.”
  • Opens discussion on observability tooling for Go ecosystems.

Read Later