CrashBreak – A new approach for production exceptions and bugs
CrashBreak – A new approach for production exceptions and bugs
Hello! Some time ago I was working on an application that had many bugs and reproducing each one was time consuming. I thought about making this process faster and more user-friendly. Recreating bugs manually in the browser by typing data and setting all connected modules in the same way like when the exception occurred can be annoying. Also, there is no certainty that the bug is reproduced in the same way it occurred. The other problem is that many of the bugs are hard to reproduce and connected to different layers of the system. The idea of CrashBreak is to reproduce the exception from the staging server on the programmer’s computer by running a request test. In order to do this the library needs to dump your system piece by piece. Currently we have 3 dumpers: for database, all request data (headers, url, body) and user session. We tried to create the whole system in an adaptive way. It means that you can write your own extensions to adapt the library to your needs. The ruby beta of the service is ready and available at crashbreak.com. Please give it a try and send me your feedback so I can make CrashBreak even better. Thank you kind strangers! Michał Janeczek
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Incorrect prediction on native model
Similar products
Flytrap – Debugging tool for fixing production bugs
Flytrap – See all I/O of functions before JS/TS production bugs
StackImpact – Java Production Profiler
POC AES implementation in C (not for production)
A rap song about squashing bugs in production
Debug Kafka faster. Reproduce production bugs locally.
AI code reviewer that catches production bugs
Your business has bugs too. Find out what they are with OHNO
Fix production bugs by replaying them locally
Tackle bugs with full context