Deployment Architecture

How do I avoid redundancy for a script running in a search head cluster?



We are currently running an alarming python script on our main search head that sends an email when less data is received than expected.

We are moving to a searchhead cluster. How do I make sure the script runs once, from a live search head, without manual intervention?

Do I copy it to all 3 search heads? Will it send me 3 emails? I want to avoid this.


0 Karma


The search head captain will designate a search head to run the search and execute the script upon a triggering condition. So the script will run once on the search head member which was designated to run the search

In a search head cluster, you use the deployer to deploy configurations to the search head members. They need to be in sync with each other, so its important that you don't add configs to the search head directly. Lastly, scripts have been deprecated from Splunk so you should really look into alert actions which can fire a script.

0 Karma
Get Updates on the Splunk Community!

Splunk Training for All: Meet Aspiring Cybersecurity Analyst, Marc Alicea

Splunk Education believes in the value of training and certification in today’s rapidly-changing data-driven ...

The Splunk Success Framework: Your Guide to Successful Splunk Implementations

Splunk Lantern is a customer success center that provides advice from Splunk experts on valuable data ...

Investigate Security and Threat Detection with VirusTotal and Splunk Integration

As security threats and their complexities surge, security analysts deal with increased challenges and ...