Monitoring Splunk

Saved Search Pre-Flight Check


Is there a way to look at a Splunk Search and check it for common issues that might cause the search to run long in advance of setting up the Search and seeing how it performs?

The process at outlines how to troubleshoot an existing bad search, but I am looking for an more automated way to call out issues prior to scheduling on the server. Looking to empower users to create their own searches, but need to ensure that they have not built the search in a way that won't scale.

Has anyone automated this check, and if so, how? If not, are there a more detailed set of steps other than the above that we could use as a starting point for a preflight check?

Any help is much appreciated. Thanks!

Splunk Employee
Splunk Employee

The Sanity Checking App should help you out here. It uses Splunk's REST API to get information about Splunk saved searches.

0 Karma