Splunk MINT App (Legacy)

Splunk MINT App User Guide

Acrobat logo Download manual as PDF

Splunk MINT is no longer available for purchase as of January 29, 2021. Customers who have already been paying to ingest and process MINT data in Splunk Enterprise will continue to receive support until December 31, 2021, which is End of Life for all MINT products: App, Web Service (Management Console), SDK and Add-On.
This documentation does not apply to the most recent version of MintApp. Click here for the latest version.
Acrobat logo Download topic as PDF

Use the Splunk MINT App

Each project in the Splunk MINT App aggregates data from a selection of mobile app projects that you created in Splunk MINT Management Console (each mobile app project corresponds to an API key). By default, an All Data project is created that contains all of your mobile app projects. You can create new projects and specify exactly which mobile app projects to include. For example, you could create a project that aggregates data from only your Android apps, or a project that contains only those apps that have been released.

To see your mobile app data aggregated in Splunk, open a project in the Splunk MINT App and view the dashboards. You can also run searches on your data with your own specific queries.

Create a new project

  1. On the Splunk Web home page, click Splunk MINT.
  2. All of your Splunk MINT projects are listed.

  3. Click Add New.
  4. Enter a project name.
  5. Optionally, select Select apps to display and select individual apps to include. (Each app that is listed corresponds to a different Splunk MINT Management Console API key.)
  6. Click Create Project.

Your new project appears on the Splunk MINT home page. Click the project name to open it and view the dashboards.


The dashboards in the Splunk MINT App contain many different categories of charts and tables displaying aggregate data for the apps you selected for your project:

  • The Analytics > Usage dashboard displays data from the user perspective, such as the number of unique users, users affected crashes, sessions (number and length), and crash rate.
  • The Analytics > Technical dashboard displays summary information about how your apps are being used, including the app versions, OS versions, mobile devices, locales, and carriers.
  • The Network > Services dashboard shows a summary of network latency, request volume, and error rate. Drill down for more information about a specific domain.
  • The Events dashboard lists the events that have occurred in your mobile apps, along with statistics for each event such as a count of occurrences, the trend of occurrences, and the number of uses that are affected by each event.
  • The Errors dashboard shows information about crashes and handled exceptions that have occurred. A summary table shows the platform, number of affected uses, and number and trend of occurences. Click an error to drill down for more information, such as stacktraces, affected users, and aggregated metrics.
  • The Transactions dashboard summarizes the rate of success, cancellation, and failure of your transactions. Drill down for more information about a specific transaction.
Note If you don't see data in the dashboards in Splunk MINT Management Console (such as network traffic or transaction data), you won't see any data in the Splunk MINT App either.

Saved reports

The Splunk MINT App provides more than 50 saved reports you can run for even more analysis. These reports are based on single searches and can include visualizations, statistics, and/or events.


Use the Splunk search language to create your own queries against the indexed data to view raw events.

  • Search on tags and fields that are defined in the MINT data model. For example:

tag=mint platform=Android device=HTC* | top 5 carrier

  • Search on fields that you define in the SDK, such as extra data (extraData) or transactions by name (tr_name). For example:

tag=mint status=SUCCESS | stats avg(tr_duration) by tr_name

  • Use the MINT sourcetypes:
    • "mint:event": Events.
    • "mint:error": Errors.
    • "mint:log": System output.
    • "mint:network": Network requests.
    • "mint:ping": Start of a session.
    • "mint:gnip": End of a session.
    • "mint:trstart": Start of a transaction.
    • "mint:trstop": End of a transaction.
  • All errors contain a field called errorHash, which groups different instances of the same error. You can use this errorHash to analyze different attributes that might be related.

Searches that use tags and fields defined in the MINT data model only work within the Splunk MINT App. If you want to create a search on MINT data from the main Search & Reporting app, search on index=mint.

Example search queries

To see events for slow network requests:

tag=mint sourcetype="mint:network" latency > 300

To display a timechart of occurrences of all events:

tag=mint sourcetype=mint:event | timechart count by event_name

To see a breakdown of a specific event by a particular extraData value:

tag=mint sourcetype=mint:event event_name="Purchase" | stats count by extraData.custom_key

To view the average memory consumption at the time of a crash:

tag=mint sourcetype=mint:error errorHash=dce17eec3cd21295877d6aef10439ce6 | stats avg(memAppAvailable)

To view the number of user affected by crashes in version

tag=mint sourcetype=mint:error appVersionName="" | timechart dc(uuid)

Last modified on 28 August, 2015
Install and configure the Splunk MINT App
MINT user roles

This documentation applies to the following versions of Splunk MINT App (Legacy): 1.1.0, 1.1.1

Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters