Splunk MINT: Is it possible to see a stack trace of a specific error instance within the grouped crashes

[JBjelicic]

The problem is that all crashes are grouped into one, and the stack trace is shown for the first one that occurred I would presume.

I can't upload a dsym file for the first couple of crashes that happened because I don't have it. But I uploaded the dsym for the last couple that happened (which are also grouped) but when I want to symbolicate the stack trace it is still asking me for the dsym of the first couple of crashes that happened.

How can I see a specific crash instance (one of the last couple ones) so that I can symbolicate the stack trace and fix my error?

[croyal_splunk · Accepted solution]

For mint.splunk.com, the symbolicated stack trace is for the first error that occurred of this type.  It is not currently possible to symbolicate a specific crash instance (one of the last couple ones).  We recommend bumping up the app version or build number to produce different error hashes for errors so they don't get grouped together.

Functionality for MINT App is the same, except in Splunk except customers can look at the raw stacktrace and symbolicate it manually if they want to see the symbols for each error.