Splunk Search

Merge app config files designed for distributed environments?

dbryan
Path Finder

I'm developing an app that will run on in an distributed environment in production, with a search head, an indexer and a forwarder.

Obviously this means that the settings in my *.conf files are split between the three roles.

In development, however, it doesn't make sense for me to have this setup as I have only a single system - I'm simply using a forwarder and an indexer.

The app is changing rapidly, and I'm trying to figure out a way to make changes easily and deploy them to dev without having to go back and change them when it's time to push releases to production.

As far as I can tell, these are my options:

  1. write a shell script to concatenate the files for the search head and indexer before pushing them to production
  2. Use a single unified file for props.conf, transforms.conf, etc. across the indexer and search head (this makes the setup less clear/maintainable in my view)
  3. Putting one of the files in default/ rather than local/ in the app directory on dev. It seems like this would work, but I'm not sure what consequences it could have, and it could lead to conflicts if I make a mistake.

Is there another way around this?

Tags (2)

dwaddle
SplunkTrust
SplunkTrust

Can you not just install both apps (fooapp-indexer and fooapp-searchhead) on the combined dev node? This is the approach I've used in the past to some success - but your problems may be more complex than mine.

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...