Go flight recorder

Go 비행 기록기

Retain a recent execution trace in a buffer until a trigger captures it.

···
html
<div class="v"><header><b>FLIGHT RECORDER</b><span id="state"></span></header><main><div class="ring" id="ring"></div><div class="snapshot" id="snapshot"></div></main><footer>rolling trace until trigger</footer></div>
css
.v{width:min(92vw,660px);height:min(86vh,310px);box-sizing:border-box;padding:clamp(9px,2.5vmin,18px);border:1px solid var(--line);border-radius:14px;background:var(--surface);display:flex;flex-direction:column;gap:7px;color:var(--fg);font:500 clamp(15px,3.2vmin,17px)/1.25 var(--font-sans, sans-serif)}.v header,.v footer{display:flex;justify-content:space-between;align-items:center;gap:8px;white-space:nowrap}.v header b{color:var(--accent);font-size:.9em}.v header span,.v footer{color:var(--muted);font-size:.82em}.v main{flex:1;min-height:0;position:relative;overflow:hidden}.v .mono{font-family:ui-monospace,SFMono-Regular,Consolas,monospace}.v .active{background:var(--accent)!important;color:var(--bg)!important;border-color:var(--accent)!important}.v .muted{opacity:.28} .ring{height:62%;display:flex;align-items:center;justify-content:center;gap:3px}.event{width:12%;height:38px;border:1px solid var(--line);border-radius:5px;display:grid;place-items:center;font:600 .78em ui-monospace,monospace}.snapshot{text-align:center;color:var(--accent);font:600 .82em ui-monospace,monospace}
js
let n=0;const events=["run","wait","run","gc","wait","run"];function draw(){document.getElementById("ring").innerHTML=events.map((x,i)=>"<div class=\"event "+(i===n?"active":"")+"\">"+x+"</div>").join("");document.getElementById("snapshot").textContent=n===4?"trigger → snapshot recent events":"new event overwrites oldest";document.getElementById("state").textContent=n===4?"capture":"recording";n=(n+1)%6}draw();setInterval(draw,750)

Go 1.25’s flight recorder keeps a recent execution trace in a low-overhead ring buffer. A trigger captures scheduling and blocking events around a problem.

Unlike storing a full trace indefinitely, new events overwrite old ones. Choose capture triggers and buffer length so the lead-up to a failure remains available.

When to use

Use it to investigate intermittent concurrency latency or goroutine stalls.

Open as page ↗