Deployment Architecture

How to change deploy-poll atomatically?

xiyangyang
Path Finder

We have 2 deployment-servers.
One is Windows which manage about 1500 Windows client servers.
One is Linux which manage about 500 Linux 20 Solaris client servers.
We wonder if there is a way to make the 2 deployment servers as backup for each other.
For example, if the Linux DS is down, Window DS is going to take care of the Linux client servers AUTOMATICALLy.
It is impossible for us to change the deploy-poll in the client servers one by one because there is too many.

0 Karma
1 Solution

esix_splunk
Splunk Employee
Splunk Employee

Splunk doesnt have this capability built in.

Your best bet would be to use dns in the case one fails.

If you your your windows DS is winds.mydomain.com and if your linux DS is nixds.mydomain.com, change DNS when one of these goes down. So if winds.mydomain.com goes down, change DNS to point to the nixds.mydomain.com server.

You need to maintain the contents of both serverclasses.conf on each DS however to account for failover.

For setting deploy-poll, I would create a custom app that sets this time. And then push this to your clients.

View solution in original post

0 Karma

esix_splunk
Splunk Employee
Splunk Employee

Splunk doesnt have this capability built in.

Your best bet would be to use dns in the case one fails.

If you your your windows DS is winds.mydomain.com and if your linux DS is nixds.mydomain.com, change DNS when one of these goes down. So if winds.mydomain.com goes down, change DNS to point to the nixds.mydomain.com server.

You need to maintain the contents of both serverclasses.conf on each DS however to account for failover.

For setting deploy-poll, I would create a custom app that sets this time. And then push this to your clients.

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