Reporting

Configuration Management

hbazan
Path Finder

Hi. We are thinking about how to do configuration management for our Splunk instance. What we need is to be sure that we can fully rebuild Splunk in case of server problems, migration, etc. I mean, can I save every configuration and saved searches/views/navigation/reports?. Our first attempt was to commit into SVN this folders: etc & share.

PS: We're not trying to do a database backup, but configurations, settings and so.

1 Solution

ziegfried
Influencer

Generally creating a regular backup of the $SPLUNK_HOME/etc directory should be sufficient. All configurations, saved searches, views, ... are located there. Using Subversion for the etc directory would work as well.

View solution in original post

0 Karma

kml_uvce
Builder

Regular backup will not work in case you overide files and you want to earliar/previous file, in svn you can get all previous files so put your files in svn if you want previous version of configuration files...

-Kamal Bisht

0 Karma

ziegfried
Influencer

Generally creating a regular backup of the $SPLUNK_HOME/etc directory should be sufficient. All configurations, saved searches, views, ... are located there. Using Subversion for the etc directory would work as well.

0 Karma

gkanapathy
Splunk Employee
Splunk Employee

The only things in share that would normally edited or site-specific would be SSL certificates for the Splunk web interface if you are using those.

0 Karma
Get Updates on the Splunk Community!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...