gotracer: Turn Go Execution Traces into Actionable Findings

go tool trace provides a browser UI for exploring Go execution traces. It works well for manual

investigation, but it doesn't fit into scripts or CI pipelines — you can't grep the output, set

thresholds, or fail a build based on what the trace contains.

The problem

Go execution traces contain detailed runtime events: GC pauses, goroutine scheduling delays, mutex

waits, syscall blocks, heap growth, and more. These don't appear in application logs or metrics —

they're only visible inside the trace.

Without a way to set thresholds or run checks automatically, there's no practical path to catching

these issues in CI. You can't fail a build because a GC pause exceeded 20ms or flag a goroutine

count that keeps growing across releases.

Teams often end up investigating traces only when something is already slow in production.

Introducing gotracer