Deployment Architecture

Syncing dashboards and alerts on multi search head architecture


We're in the process of doing a major upgrade to our Splunk environment. We're effectively moving from a single instance of Splunk doing everything to a "future-proof" setup with multiple indexers, multiple search heads and a separate deployment server.

I'd like to understand what best practice is for how dashboards and alerts should be set up in such an environment.

  1. With 2 or more search heads does a dashboard created on one search head appear on another search head? How do we achieve this? We plan on placing a load balancer in front of our search heads to distribute user load.
  2. How do alerts work? If we create an alert by logging into one of the search heads can we then configure it on the other search head? If it appears on both search heads does the alert run twice?

Thanks for any advice!

Splunk Employee
Splunk Employee

Search head clustering ( was introduced in Splunk Enterprise 6.2, released on October 28, 2014. A search head cluster captain ( coordinates activities among all cluster members. The responsibilities/activities include:

  • Scheduling jobs
  • Coordinating alerts and alert suppressions across the cluster
  • Pushing the knowledge bundle to search peers
  • Coordinating artifact replication
  • Replicating configuration updates

Also see:

Migrate from a standalone search head to a search head cluster

Use the deployer to distribute apps and configuration updates

How do you set app permissions in a search head cluster

0 Karma

Path Finder

I have the same question and would appreciate any input on the topic.
also, how to manage user settings in fore-mentioned environment when users access different search head and view the same dashboard ?

0 Karma
.conf21 Now Fully Virtual!
Register for FREE Today!

We've made .conf21 totally virtual and totally FREE! Our completely online experience will run from 10/19 through 10/20 with some additional events, too!