Splunk Enterprise

SplunkUniversalForwarder instanceName = none

cjpote
Explorer

Some cloned Red Hat Enterprise Linux 7 systems show blank "Instance Name" values on my deployment server's Forwarder Management tab, and when executing ./splunk list deploy-clients, the forwarders instanceName value is shown as "none".
Where is the instanceName value set?

0 Karma

adonio
Ultra Champion

check /splunkforwarder/etc/system/local/inputs.conf and /splunkforwarder/etc.system/local/server.conf
hope it helps

0 Karma

cjpote
Explorer

Sorry, I should have mentioned that I already verified the "serverName = " value in $SPLUNK_HOME/etc/system/local/server.conf, and "host = " in $SPLUNK_HOME/etc/system/local/inputs.conf. They are both set to the same value returned by the "hostname" command on the system.

I also verified that "$SPLUNK_HOME/bin/splunk cmd btool [server|inputs] list --debug" shows the correct serverName and host values; but neither one of those shows an "instance(Name) = " value.

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