<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to disable hostname chaining? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-disable-hostname-chaining/m-p/10612#M385</link>
    <description>&lt;P&gt;There are two alternative solutions for this issue:
&amp;gt;&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
  &lt;OL&gt;
  &lt;LI&gt;&lt;P&gt;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:
  &lt;A href="http://linux.die.net/man/5/syslog-ng.conf" rel="nofollow"&gt;http://linux.die.net/man/5/syslog-ng.conf&lt;/A&gt;
  Look for "chain_hostnames"&lt;/P&gt;&lt;/LI&gt;
  &lt;LI&gt;&lt;P&gt;Create a props.conf file under your $SPLUNK_HOME/etc/apps/SplunkEnterrpiseSecuritySuite/local with below content:&lt;/P&gt;&lt;/LI&gt;
  &lt;/OL&gt;
  
  &lt;P&gt;[syslog]
  TRANSFORMS = syslog-header-stripper-ts-host, syslog-host&lt;/P&gt;
  
  &lt;P&gt;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.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;</description>
    <pubDate>Sat, 27 Mar 2010 05:22:15 GMT</pubDate>
    <dc:creator>zliu</dc:creator>
    <dc:date>2010-03-27T05:22:15Z</dc:date>
    <item>
      <title>How to disable hostname chaining?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-disable-hostname-chaining/m-p/10611#M384</link>
      <description>&lt;P&gt;How to disable hostname chaining? Splunk picks the chained hostname rather than the original.&lt;/P&gt;</description>
      <pubDate>Sat, 27 Mar 2010 05:19:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-disable-hostname-chaining/m-p/10611#M384</guid>
      <dc:creator>zliu</dc:creator>
      <dc:date>2010-03-27T05:19:32Z</dc:date>
    </item>
    <item>
      <title>Re: How to disable hostname chaining?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-disable-hostname-chaining/m-p/10612#M385</link>
      <description>&lt;P&gt;There are two alternative solutions for this issue:
&amp;gt;&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
  &lt;OL&gt;
  &lt;LI&gt;&lt;P&gt;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:
  &lt;A href="http://linux.die.net/man/5/syslog-ng.conf" rel="nofollow"&gt;http://linux.die.net/man/5/syslog-ng.conf&lt;/A&gt;
  Look for "chain_hostnames"&lt;/P&gt;&lt;/LI&gt;
  &lt;LI&gt;&lt;P&gt;Create a props.conf file under your $SPLUNK_HOME/etc/apps/SplunkEnterrpiseSecuritySuite/local with below content:&lt;/P&gt;&lt;/LI&gt;
  &lt;/OL&gt;
  
  &lt;P&gt;[syslog]
  TRANSFORMS = syslog-header-stripper-ts-host, syslog-host&lt;/P&gt;
  
  &lt;P&gt;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.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Sat, 27 Mar 2010 05:22:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-disable-hostname-chaining/m-p/10612#M385</guid>
      <dc:creator>zliu</dc:creator>
      <dc:date>2010-03-27T05:22:15Z</dc:date>
    </item>
  </channel>
</rss>

