Introduction

This documentation covers the SCMA App hosted on Splunkbase and installed in customer-managed Splunk installations. Before running the checks, always validate that the latest version of the app is being utilized.

Important — Supported Splunk versions

Review the supported Splunk Enterprise compatibility list on Splunkbase before deploying. As of 2026, Splunk Support covers Enterprise versions 9.3, 9.4, 10.0, and 10.2 only. All versions 9.2 and below are End of Support. For unsupported versions, contact Splunk Professional Services.

Source: Splunk Software Support Policy (last updated December 2025)

What the SCMA app does

The SCMA runs a series of checks — called KPIs (Key Performance Indicators) — against a customer's Splunk deployment. These KPIs give insight into the health and capacity of the environment and are automatically compared against the public Splunk Cloud Service Description and internal Sweet Spot documentation to assess cloud-migration fit.

The KPIs also drive the automatic production of a draft Statement of Work (SOW) for Professional Services.

Key features

  • Runs checks serially to minimize customer environment impact
  • Check execution framework using custom JavaScript and Python scripts (since v5.0) — no 10-minute search timeout
  • Checks continue running even if you navigate away or reboot your computer
  • Each check writes results to _introspection index, enabling checks to be run days apart
  • Results retained for 30 days; only the latest run is included in exports
  • Export formats: ZIP archive, CSV, DOCX, JSON parameters for PS LOE and Stack Composer sizing
  • Inline SCMA Review dashboard for reviewing results without exporting (v5.2.5+)
Section What you'll find
Installation & Setup Standard installation, who to run as, Splunk Islands, upgrades, Preflight dashboard
How Checks Work Check execution, export options, FedRAMP considerations, performance, file uploads
Checks Reference All 60+ checks with check number, SCMA-ID, purpose, and details
Troubleshooting Guide 5-step troubleshooting process and common failure scenarios
FAQ Answers to FAQ-001 through FAQ-013
How-To Guides Support case creation, MC configuration examples, import steps, advanced runbooks