Segmenting Crashes in Crash Reporting

Is there a way to include high-level “markers” for Performance Reporting (similar to profiler samplers, but at a massively coarser scope) so that we can say “This crash is happening in Level X” or “This Crash Happens During the Create Player Feature” or similar?

I’m specifically interested in native crashes (because with exceptions I can always catch them myself and debug.logexception them myself).

This would be hugely helpful in reproducing apparently high-repo in-the-wild crashes that we can’t figure out how users are making happen.

@ferretnt — thanks for the feedback. We have a couple features on our backlog that we think will allow you to achieve this.