Free tools for debugging production errors
Small tools for the jobs around a production error: reading a trace, decoding a minified bundle, digging through logs, checking what an uptime target allows. Each one runs in your browser and sends nothing anywhere. When you want your coding agent to read the errors themselves, that is what Runheed is for.
- Source map stack trace decoder
Drop a .map file, paste a minified JavaScript stack trace and get the original file, line and column for each frame. Runs in your browser.
- Uptime and SLA downtime calculator
Turn an uptime percentage like 99.9% into allowed downtime per day, week, month and year, or turn downtime back into an uptime percentage.
- Error budget calculator
Enter an SLO target and your request volume to see how many failed requests the error budget allows and how fast you are burning it.
- Stack trace formatter
Paste a messy JavaScript, Python, Ruby or Go stack trace and get it cleaned up, one frame per line, with your own code highlighted.
- JSON log viewer
Open a JSON-lines log file in your browser, filter by level and field, and hide noisy fields. The file never leaves your device.
- HTTP status code reference
Every HTTP status code with a plain meaning and when an app should send it, including 400 vs 422, 401 vs 403 and 502 vs 504.