Deployment Architecture

When using the deployment server, what is the difference between local and default directories?

brent_weaver
Builder

I am using the deployment server and it has been my company's practice to put inputs.conf files in local. Is this where it belongs? It would seem that local would take precedence over default and is used to very specific site logging needs? Am I way off base here? Toto, is this Kansas 🙂

Thanks!

woodcock
Esteemed Legend

The best policy is that the AUTHOR of the app puts it into default and everyone else writes into local. When you download an app from apps.splunk.com you will find that all of the author's stuff is in default and nothing is in local and when you deploy these apps from your DS, you should not modify this. Also, when you write your own proprietary apps that are for internal use only, when you put them on the DS, they should use default, not local. So the general rule is that if it is on the DS, it should be using default UNLESS you are making a modification to something that is distributed with the base Splunk distribution (e.g. '$SPLUNK_HOME/etc/system//.conf); in that case you make your proprietary changes inside$SPLUNK_HOME/etc/system/local*.confand NEVER touch anything inside anydefault` directory that came from your original installation of Splunk binaries.

Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...