Getting Data In

Hostname macro in inputs.conf

afx
Contributor

Hi,
I have a Linux based application server that exists in two copies on xhostA and xhostB.
I am getting their syslog output via a localhost syslog interface into the UF which is installed on those hosts.

I do not want to push individual inputs.conf files. So how to I get the appropriate host name for the syslog input?
If I leave host emtpy, I get 127.0.0.1 which is not helpful. When I set the hostname, it then is identical for both systems.

[udp://127.0.0.1:8514]
connection_host = 127.0.0.1
sourcetype=linux_secure
no_appending_timestamp = true
index= xauth

Any ideas on how to rectify this easily?
I assume that

host=$decideOnStartup

would just deliver 127.0.0.1 as leaving host empty results in this.

thx
afx

0 Karma
1 Solution

afx
Contributor

Ok, to answer my own question...
In contrast to what I assumed, $decideOnStartup is resolved to the real hostname and not the referenced address of the input like the default for host.

View solution in original post

0 Karma

afx
Contributor

Ok, to answer my own question...
In contrast to what I assumed, $decideOnStartup is resolved to the real hostname and not the referenced address of the input like the default for host.

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...