Unreadable stacktraces in crash reports

Hello there,

I have setup my crash reporter to send crashes to Sentry. I receive stack traces and all, it is a great tool as long as a source of crash happens in my C++ files. I see it where it happened, I fix it, simple.

But my UI for instance is built entirely on blueprints and stack traces are simply unreadable. There are a lot of references to internal engine stuff and not even one hint on where the problem might be in blueprints.

So do I necessarily have to rewrite blueprint logic in C++ or there is a better way to see what crashed exactly?