What if we place the deploymentclient file under the system/default as well as under the app/local?

[abhi04]

What if we place the deploymentclient.conf in the forwarder inside the system/default as well as under the app/local.

for e.g.

1. under the system/default:

deploymentclient.conf

[deployment-client]
clientName = xyz
phoneHomeIntervalInSecs = 5

[target-broker:deploymentServer]
targetUri = xxx

2. under the app/local

deploymentclient.conf

[deployment-client]
phoneHomeIntervalInSecs = 3600

Will the phone home take place after 3600 sec due to the higher precedence?

[skakehi_splunk]

FYI. Be careful. Modify the configuration with system/default files are not recommend.

If you upgrade the Splunk or Forwarder, all of under system/default configuration files override to new one. It means you'll lost your customize settings with system/default.

On the global context, system/local is the most higher precedence. (or App local is good)

[burwell]

You should check out btool to find out which configs are in effect.

/opt/splunk/bin/splunk btool deploymentclient list --debug

You will see where the configs from each file come from. 

[richgalloway · Accepted solution]

Yes, the local file has priority. See https://docs.splunk.com/Documentation/Splunk/8.0.4/Admin/Wheretofindtheconfigurationfiles

If your problem is resolved, then please click the "Accept as Solution" button to help future readers.