I'd like to use a single DNS entry on all of my forwarders, and have the deployment server send traffic for my secondary environment to the secondary deployment server.
In the primary deployment server environment, where the DNS entries is pointing to, I tried setting up a tenants.conf
[tenant:dit]
whitelist.0 = secondary_environment_hostname_prefix*
and a pubsub.conf
[pubsub-server:dit]
targetUri=secondary_deployment_server:18089
The documentation gives hints at this topology, although mostly focuses on handling multiple serverclass.conf files.
I’ve been reviewing these pages:
http://docs.splunk.com/Documentation/Splunk/5.0.4/Deploy/Deployinmulti-tenantenvironments
http://docs.splunk.com/Documentation/Splunk/5.0.4/Admin/Tenantsconf
http://docs.splunk.com/Documentation/Splunk/latest/Admin/Pubsubconf
I saw some documentation on how to make one deployment server a client of the other, but I doesn’t sound like that is an appropriate solution for what I’m trying to achieve.
Any creative ideas out there?
... View more