4 ms·
How would Lightrun have helped here? Skimming their docs, it looks like a fancy debugger that can log stuff on prod and display it in your IDE. A debugger is m
by sa46 4y ago
How would Lightrun have helped here? Skimming their docs, it looks like a fancy debugger that can log stuff on prod and display it in your IDE.
A debugger is most useful when you know where the problem is and you can either reproduce it or it occurs often enough to observe. Neither was true for OP. Additionally, the problem was in nginx and it's not clear if the error was visible from a part of the stack that Lightrun supports.
That said, I'm always game to hear about alternative debugging techniques.
- invalidname 4y agoThis is classic for a tool like that... You know an email isn't sent to some users. You start placing conditional snapshots (like conditional breakpoints but they don't stop) in key locations. You can use conditions like "currentUser == 'user experiencing problem'". Or you can place the snapshots in places where code "should" reach in case of error. Go make coffee. Come back and you'll see stack traces and variable values you can analyze to see the problem. The nice thing is that it will even work if you have a cluster. Just place the snapshot in a tag which applies to all the servers. You don't need to update the code, there's no risk involved etc.