Use one forwarder to act as deployment manager to other forwarders

anz_leycurav — Fri, 16 May 2014 03:30:56 GMT

Hi,

I have a couple of heavy forwarders to monitor a particular platform, each one for a specific context (dev / test / prod). there is a central indexer with a working deployment manager where, for various reasons, I prefer not to put the config I want to be deploying to my above-mentioned forwarders.

This appears to be a problem in the forwarder management setup on my "main" forwarder as the host names of the "other" forwarders do not appear to be recognized. I can't find anything in the docs that would hint at a restriction, but I can't find either where to define my "other" forwarders as clients to the "main" one. I can see serverclass.conf has been added after I saved the "Edit Clients" page, I also tried bouncing the forwarder but no list of possible client hosts are coming up.

What am I missing pls?

Thanks Vincent.

Re: Use one forwarder to act as deployment manager to other forwarders

anz_leycurav — Fri, 16 May 2014 03:45:28 GMT

Sorted - I missed the bit documented here: http://wiki.splunk.com/Deploy:DeploymentServer

the "phoning" has to be enabled on the "other" forwarders.

topic Re: Use one forwarder to act as deployment manager to other forwarders in Getting Data In

Use one forwarder to act as deployment manager to other forwarders

Re: Use one forwarder to act as deployment manager to other forwarders