I had a customer recently ask how to change the host that was applied to a particular set of incoming events. Normally this wouldn’t be a big deal, just specify the new name in inputs.conf. But this is from syslog. When you set one of the syslog sourcetypes there is some extra processing to extract the correct hostname which overrides other settings. And the hostname in the event is wrong.
So to get the right one, I set up this transform to force it to a specified value. And still give it my correct syslog sourcetype.
My inputs.conf is tailing an entire directory, which for sake of demonstration I’m going to pretend is all syslog.
$ more inputs.conf host = support09.splunk.com [tail:///var/log] disabled = false host = support09.splunk.com sourcetype = syslog
props.conf is specifying a transform only for the source of interest:
$ more props.conf # note: overriding default syslog transform! TRANSFORMS = feorlenhost
and transforms.conf is defining what to do to it. I have to specify a REGEX, but I’m not actually using it so I’ll just say ‘.’ to match everything. The FORMAT line is what is going to set my host:
$ more transforms.conf [feorlenhost] DEST_KEY = MetaData:Host REGEX = . FORMAT = host::feorlenhost.splunk.com
So whatever syslog put in there for host, ignore and use my static value instead.
The world’s leading organizations rely on Splunk, a Cisco company, to continuously strengthen digital resilience with our unified security and observability platform, powered by industry-leading AI.
Our customers trust Splunk’s award-winning security and observability solutions to secure and improve the reliability of their complex digital environments, at any scale.