With OverOps, you go deep on Java, with every variable value, overlaid on the code across the call stack. Without looking at / relying on logs.
There's a short video here (http://www.overops.com/) and you can see some more samples after you sign up.
I noticed the sentry json API at least supports them, so this may be a limitation of the specific language SDK as currently stands:
https://docs.sentry.io/clientdev/interfaces/stacktrace/ (see "vars")
(I'm fiddling around with writing a Windows C++ SDK for sentry with a C ABI...)
Note that in your browser JS use case, we capture breadcrumbs to show you console logs, user interaction events, XHRs, navigation events, prior errors, etc leading up to the error, so you should be able to easily just reproduce the error state rather than digging through logs to find out what it was. If you still find yourself needing to dig through logs to troubleshoot JS errors reported via Sentry, I'd really like to hear more about your experience to see if we can make it better.