Hi, we're trialling the Splunk MINT App on SplunkCloud/Enterprise and also on the old MINT Management Console.
It looks like the MINT App's functionality is quite limited in displaying Errors (no breadcrumbs, no custom data set with Mint.logException('dataname', 'datavalue', ExceptionInstance) ), so we're now focussing at evaluating the MINT Management Console UI.
Is there a way to control the grouping of the Exceptions/Crashes? I understand there's an errorHash property which likely includes the stackTrace content. However our Android stacktraces often diverge from about the 4th line even for errors that we wish to have grouped together, so without being able to enforce manual grouping, or without Splunk agreeing to change the way the grouping works (e.g. by only taking into account line 1 of the stacktrace), Splunk MINT won't fit the bill for us.
Is there any way to control the grouping? Some competing tools e.g. allow to create grouping rules in the Dashboard UI after the exception data is ingested, or alternatively we could give you a custom hash as part of the exception payload - if there was an API to allow this in the SDK.
Also, we're quite surprised that the "View Logs" link for each individual Error Instance doesn't show Logcat output for the specific instance (despite the URL of the link being error instance-specific). Is this a bug that will be fixed?
MINT Management Console (MMC) is designed to give developers an overview of their mobile apps but not a complete picture. See the Differences here. On MINT App, data is raw and unfiltered. MMC uses sampled data.