Deployment Architecture
Highlighted

What happens when changing deployment servers?

SplunkTrust
SplunkTrust

In order to test configurations before going to production we want to set forwarders to go to our development environment to get inputs and parsing configured properly.

The idea is to script an install that points to our dev environment that will then receive apps based on the server classes that point to the indexer cluster and set some default settings for the forwarder. These apps will be similar across both environments but have addresses and such changed.

From there we would develop a TA in dev for the inputs and parsing for the sourcetype and create a new server class to receive the TA (would also have to go in master-apps for the parsing portion to be done on the indexers). Once everything looks good we want to copy over the TA and create the server class in production and change the deploy poll of the forwarder to the production deployment server.

When the deployment server address is changed do the apps from the dev environment automatically get replaced by the ones in the production environment?

0 Karma
Highlighted

Re: What happens when changing deployment servers?

Super Champion

We faced the same issue in our enterprise installations. What I do is, create a good naming convention for the "serverclasses". (Assume my company name is ABC)
So I will have

  • ABCdevTA-deployments_serverclass
  • ABCtestTA-deployments_serverclass
  • ABCprodTA-deployments_serverclass

Using your build mechanism, you can put anything with prod to PRODUCTION etc.
You can have the flexibility to have required TA's within each serverclass, so it can be flexible to any degree

0 Karma