Getting Data In

How to disable hostname chaining?

zliu
Splunk Employee
Splunk Employee

How to disable hostname chaining? Splunk picks the chained hostname rather than the original.

Tags (2)
0 Karma
1 Solution

zliu
Splunk Employee
Splunk Employee

There are two alternative solutions for this issue: >

  1. Modify the configuration of syslog server to disable hostname chaining. This is the preferred method since it removes one of the moving parts in this equation and ensures that events being sourceypted as syslog that do not have a chained hostname are not impacted Below is a link for syslog-ng.conf reference: http://linux.die.net/man/5/syslog-ng.conf Look for "chain_hostnames"

  2. Create a props.conf file under your $SPLUNK_HOME/etc/apps/SplunkEnterrpiseSecuritySuite/local with below content:

[syslog] TRANSFORMS = syslog-header-stripper-ts-host, syslog-host

This will tell Splunk to remove the the chained hostname and timestamp from the event and then extract the hostname from the newly modified event.

View solution in original post

zliu
Splunk Employee
Splunk Employee

There are two alternative solutions for this issue: >

  1. Modify the configuration of syslog server to disable hostname chaining. This is the preferred method since it removes one of the moving parts in this equation and ensures that events being sourceypted as syslog that do not have a chained hostname are not impacted Below is a link for syslog-ng.conf reference: http://linux.die.net/man/5/syslog-ng.conf Look for "chain_hostnames"

  2. Create a props.conf file under your $SPLUNK_HOME/etc/apps/SplunkEnterrpiseSecuritySuite/local with below content:

[syslog] TRANSFORMS = syslog-header-stripper-ts-host, syslog-host

This will tell Splunk to remove the the chained hostname and timestamp from the event and then extract the hostname from the newly modified event.

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