Skip to content
#0198
Browser

The console.error fires; the network spike happens; you see both

A customer reports the dashboard hangs intermittently. You can't reproduce it locally. Your APM only sees server-side spans.

You point a Hoody Browser at the customer's exact route, with their cookie, and let it sit. Every minute, a cron pulls GET /console?since=... and GET /network?since=.... Both are 500-entry ring buffers held by the browser instance. The since parameter walks the buffer forward without missing entries.

When the hang happens at 14:22, the data is right there: a console.error from the analytics SDK, eleven simultaneous fetch calls to /api/widgets, a 504 on the slowest. You file the bug with the timestamp aligned across both logs.

DevTools used to be a panel you opened. Now it's a URL you GET.