Deployment Architecture

splunk Deployment server

kholleran
Communicator

When we first rolled out Splunk, the deployment server was not used. Its been a while now & I want to move to a deployment server architecture. My question is:

Should I remove everything from etc/system/local that was put on the individual instances of Splunk or can I leave that and will the deployment apps override those?

Thanks.

Kevin

Tags (1)
0 Karma
1 Solution

tskinnerivsec
Contributor

deployment apps will not over write the settings in etc/system/local. You may find that you have some settings configured in etc/system/local that make more sense managing with a deployed application. If that is the case, you would have to comment out the setting in etc/system/local so that the application would control the setting. I would start out deploying apps one at a time to migrate system/local settings that make sense. Then most of the apps you deploy can contain new inputs or other functionallity.

View solution in original post

tskinnerivsec
Contributor

deployment apps will not over write the settings in etc/system/local. You may find that you have some settings configured in etc/system/local that make more sense managing with a deployed application. If that is the case, you would have to comment out the setting in etc/system/local so that the application would control the setting. I would start out deploying apps one at a time to migrate system/local settings that make sense. Then most of the apps you deploy can contain new inputs or other functionallity.

kholleran
Communicator

That's what I was figuring but I wanted to make sure. I have basically migrated all settings for inputs/outputs/transforms/etc from conf files in /etc/system/local to their own apps to be managed, so its a matter of removing these from the conf files & syncing with the deployment server.

Thanks for your help.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...