Race condition bugs are very tricky to reproduce indeed. While there will never be a guarantee our Live Replay will reproduce your issue - it should be possible since we replay all events in the exact sequence they were recorded. Our replay studio also has a 'Preserve timing' setting which uses the same delay between the events.
You could, but the point is that the stacktrace is useless in most apps (unless you have stateless minimalist website). As soon as you make a web app and you have state - stacktrace doesn't help reproduce the bug.
You sum it up well. If you just get static text (call stack etc) from your error logger tool, it's of almost no use as it doesn't reveal the state of the app. With modern tools that have replay capability, this changes and the debugging process is so much nicer. :)
Every error tracker I've ever used allows you to send arbitrary data (which could be your entire flux store, for example) and has great documentation on how to start using it.
We also allow you to attach any custom data to the error report. But this doesn't necessarily help you put the web application into the state where it crashes. Demo of custom data:
And, it's not just about production sites - another use case is using this internally as a tool between QA <-> Developers to speed up communication when new errors are found.
https://sting.co/ https://www.abi.se/ and lots more listed at https://www.sisp.se/medlemmar