topic Re: Best Practice for copying dashboards and apps between Splunk Enviroments in All Apps and Add-ons

Best Practice for copying dashboards and apps between Splunk Enviroments

chazilla44 — Thu, 02 Jul 2015 00:32:18 GMT

Hello,

I have multiple Environments each with a distributed deployment with various indexers, search heads and forwarders. I like many have setup alot of apps and dashboards in my DEV/UAT environment. My question is I want to use the same Dashboards and Apps in my other Environments i.e. IAT, PROD etc..

I know you can easily export the dashboard XML and searches and write them into the envirnonments and then download the actual apps on the deployment server in each environment and push out but I was wondering if anyone knew of a more structured way to do both without basically starting over in each environment.

Thanks,

Chad..

Re: Best Practice for copying dashboards and apps between Splunk Enviroments

woodcock — Thu, 02 Jul 2015 01:59:03 GMT

That is what I do, make the dashboards an app and use DS.

Re: Best Practice for copying dashboards and apps between Splunk Enviroments

martin_mueller — Thu, 02 Jul 2015 08:19:13 GMT

The App Exporter at https://splunkbase.splunk.com/app/2613/ can help you export your apps from DEV to later import them in IAT and PROD.

Re: Best Practice for copying dashboards and apps between Splunk Enviroments

ncsantucci — Thu, 02 Jul 2015 10:11:05 GMT

While I don't know your deployment topology (distributed deployment or not, or even if you have multiple deployment servers)...

If you have multiple deployment servers, there is a so-called Multi-tenant scenario "Example: How to propagate apps from Primary to Secondary Deployment Server" http://wiki.splunk.com/Deploy:DeploymentServer (which will be unsupported in the next major release of Splunk 7.0). More details straight from the docs: http://docs.splunk.com/Documentation/Splunk/6.2.3/admin/Tenantsconf. There is another Answers post on this method: http://answers.splunk.com/answers/60559/can-one-deployment-server-send-data-to-another-deployemnt-server.html
If you version control your apps in say Git (or some other version control system), you can check in your config apps which live on say on DS1 (deployment server one for DEV/UAT), then you can pull down your config apps on DS2 (deployment server two for ITA, etc.), then reload the deployment server.

In a distributed deployment, which most large enterprise environments have due to having data collected from multiple data centers, method 2 might be your best bet!

Good luck!

Re: Best Practice for copying dashboards and apps between Splunk Enviroments

chazilla44 — Thu, 02 Jul 2015 14:49:55 GMT

Hi,

2 seems the most logical. They are not version controlled. However, what about the dashboards I created in my App in DEV what is the best way to move them over. Is this just copying the XML over or would moving the apps include the dashboards associated with those apps?

Re: Best Practice for copying dashboards and apps between Splunk Enviroments

martin_mueller — Thu, 02 Jul 2015 15:33:09 GMT

Dashboards shared within an app or globally will get moved over after exporting the app from one stage and importing it in the next. You can verify this by looking at $SPLUNK_HOME/etc/apps/your_app/local/data/ui/views, this should contain your XML files. Export the app using the App Exporter I linked to above, grab the .spl file, open it with a tar.gz capable tool and navigate to the same path - you should find your XML files again.

Re: Best Practice for copying dashboards and apps between Splunk Enviroments

chazilla44 — Thu, 02 Jul 2015 15:43:41 GMT

Is the App Exporter only linux compatible or do you have a zip version for windows? The enviroment is only windows not linux?

Re: Best Practice for copying dashboards and apps between Splunk Enviroments

martin_mueller — Thu, 02 Jul 2015 15:55:42 GMT

It's platform independent, and I'm using it at a customer on 2008R2.