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 Splunk MINT App (Legacy). For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

Requirements

Software requirements

The requirements for the Splunk MINT App are:

  • Splunk Enterprise 7.2.x, 7.3.x
  • Splunk Enterprise 8.0.0, Python 2 and Python 3
  • Splunk Enterprise 8.1.0, Python 2 and Python 3
  • The Splunk MINT Add-on.

Hardware requirements

Before you install Splunk MINT App, see the Splunk Enterprise Capacity Planning Manual for information about hardware capacity planning, deployment scaling, hardware recommendations, and performance recommendations.

For reference hardware, see Reference machine for distributed deployments in the Capacity Planning Manual.

Capacity planning for search heads and indexers

Use the following guideline for capacity planning for search heads and indexers:

Expect an indexing volume of 20GB/day for every 1 million monthly active users (MAU)

The indexing volume of data that is collected by Splunk MINT depends on the complexity of your instrumented mobile apps, the number of sessions, and the length of sessions. Based on your daily indexing volume and the number of Splunk users you expect, use the guidelines in Summary of performance recommendations in the Capacity Planning Manual to plan the capacity for your search heads and indexers.

Capacity planning for heavy/light forwarders

Use the following guideline for capacity planning for heavy/light forwarders:

Use at least one forwarder with the MINT modular input per 10 million MAU

The MINT Data Collector can cache 100MB of raw data.

  • You might experience a loss of data if you don't pull data fast enough or if there is sudden spike in traffic.
  • The cached data in the MINT Data Collector will be purged if you don't pull data for 24 hours.


To avoid data loss, you should properly provision forwarders that run the Splunk MINT modular input, which is part of the Splunk MINT Add-on package, and configure these forwarders to continuously retrieve data from the MINT Data Collector. The MINT Support team will contact you if you need more forwarders due to increased traffic.

Last modified on 12 October, 2020
PREVIOUS
Learn more and get help
  NEXT
Install and configure the Splunk MINT App

This documentation applies to the following versions of Splunk MINT App (Legacy): 3.0.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