Universal Forwarder and splunk-launch.conf

[hectorvp]

Does anything change in universal forwarder if I change the servername ???

SPLUNK_SERVER_NAME=SplunkForwarder1234 ???

I checked in linux by systemctl status, I didn't find any change in splunk daemon, it was named as "splunkd" itself .

Or is it only affect for Windows OS service in an UF??

PS: I know it shouldn't be changed ideally, but still experimenting few things...

[isoutamo · Accepted solution]

Hi

you could update 

SPLUNK_SERVER_NAME=splunk-uf

on  splunk-launch.conf and then enable boot start.

r. Ismo

[hectorvp]

Thanks,for the answer @isoutamo .

Meanwhile I'm concerned with this as well:(below)

Will this cause any issue in UFs working???

I'm doing this because we are installing two splunk UFs on single Linux host, then we would need to identify the services of these 2 splunk UFs.

We are installing two splunk UFs because the server is used by our vendors and us as well and we aren't using same Splunk enterprise to manage it with just creating different apps at deployment servers.(business policies won't allow to use single management server)

There can be other alternatives like using Rsyslog but I find UFs more reliable than any other tools, So I'm experimenting this.

But will it have official Splunk support?

[isoutamo]

As long as those installations have separate paths, ports and unit-files I don't see any issues there. Of course when you are updating those then that's is best to do from tar.gz files instead of rpm.

That should be supported by splunk as instructions for change that names are in their documentation.

r. Ismo

[hectorvp]

Thanks for the quick response @isoutamo