Deployment Architecture

Deployment Server over old config management

mwdbhyat
Builder

Hi there,

What is the best way to approach attaching a DS to an environment that is already in place and scattered with apps? In terms of inputs/outputs etc.

EG there were inputs.conf in random apps on forwarders. These are still there forwarding. However when I connect the new DS to these,  inputs.conf will be in new <appname>/appstructure. So it would be deployed alongside the current inputs.conf, rather than overwrite whats there - would this mean that the files being monitored would be ingested twice? How do i go about removing the old config and using the new without either duplicating or having data gaps?

My plan for all other apps including outputs.conf will be to deploy those first, then remove anything from the "old" config manually. As the DS previously didnt manage these old dodgy apps, it will not autoremove them. This is what made me curious about there being duplicate data as mentioned above. 

What are your thoughts on this ?

Thanks!

Labels (2)
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Splunk merges config files from apps before it decides what to do so, no, having multiple input.conf files will not result in duplicate inputs.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Splunk merges config files from apps before it decides what to do so, no, having multiple input.conf files will not result in duplicate inputs.

---
If this reply helps you, Karma would be appreciated.
Get Updates on the Splunk Community!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...