<?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: Modify sourcetype host extraction in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Modify-sourcetype-host-extraction/m-p/102206#M21437</link>
    <description>&lt;P&gt;Add the config to props.conf on the &lt;STRONG&gt;indexer&lt;/STRONG&gt;. (See &lt;A href="http://www.splunk.com/wiki/Where_do_I_configure_my_Splunk_settings%3F" target="_blank"&gt;here&lt;/A&gt;, noting that Universal and Light Forwarders work the same way.) This will affect all data with sourcetype &lt;CODE&gt;syslog&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[syslog]
# yes, the next line sets it to an empty value
TRANSFORMS =
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This overrides the default in &lt;CODE&gt;$SPLUNK_HOME/etc/system/default/props.conf&lt;/CODE&gt;, of &lt;CODE&gt;TRANSFORMS = syslog-host&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;There are a few other versions of syslog in the defaults (e.g. cisco_syslog, windows_snare_syslog) that will have their own config that you would have to override separately if you desire.&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 09:33:49 GMT</pubDate>
    <dc:creator>gkanapathy</dc:creator>
    <dc:date>2020-09-28T09:33:49Z</dc:date>
    <item>
      <title>Modify sourcetype host extraction</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Modify-sourcetype-host-extraction/m-p/102205#M21436</link>
      <description>&lt;P&gt;I noticed that I receive logs from a single linux system with two different host names. &lt;/P&gt;

&lt;P&gt;Some inputs are files in the &lt;CODE&gt;/var/log/apache2&lt;/CODE&gt; directory.&lt;BR /&gt;&lt;BR /&gt;
These are delivered as coming from &lt;STRONG&gt;lvps87-230-26-17.dedicated.hosteurope.de&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;
The &lt;STRONG&gt;sourcetype&lt;/STRONG&gt; of this input is &lt;STRONG&gt;access_common&lt;/STRONG&gt;.&lt;/P&gt;

&lt;P&gt;Another input is &lt;CODE&gt;/var/log/auth.log&lt;/CODE&gt;&lt;BR /&gt;&lt;BR /&gt;
These log lines are delivered as coming from &lt;STRONG&gt;&lt;CODE&gt;lvps87-230-26-17&lt;/CODE&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;
The &lt;STRONG&gt;sourcetype&lt;/STRONG&gt; is &lt;STRONG&gt;syslog&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;I understand that the sourcetype syslog does not take the FQDN, but I would like to change that and dont know where to find that configuration.&lt;/P&gt;

&lt;P&gt;The linux host delivers by the &lt;STRONG&gt;Universal Forwarder&lt;/STRONG&gt; to my Splunk index server. It is not a TCP or UDP Input.&lt;/P&gt;

&lt;P&gt;Is there anyone with a solution to this issue?&lt;/P&gt;

&lt;P&gt;---- 1 hour later ----&lt;/P&gt;

&lt;P&gt;I noticed that splunk &lt;STRONG&gt;does not&lt;/STRONG&gt; take the host name of the &lt;STRONG&gt;Universal Forwarder hostname&lt;/STRONG&gt; as the database field "host" if the &lt;STRONG&gt;sourcetype&lt;/STRONG&gt; is &lt;STRONG&gt;syslog&lt;/STRONG&gt;.   &lt;/P&gt;

&lt;P&gt;It actually &lt;STRONG&gt;extracts the hostname from the log line&lt;/STRONG&gt; which is quite useful in the case that several hosts are logging into a single syslog-file. (in my case auth.log)&lt;/P&gt;

&lt;P&gt;What I did to avoid the duplicate host name entries was:&lt;BR /&gt;&lt;BR /&gt;
I changed the syslog-ng options of my system from options &lt;STRONG&gt;&lt;CODE&gt;use_fqdn(no)&lt;/CODE&gt;&lt;/STRONG&gt; to &lt;STRONG&gt;&lt;CODE&gt;use_fqdn(yes)&lt;/CODE&gt;&lt;/STRONG&gt; &lt;/P&gt;

&lt;P&gt;Nevertheless - I would like to know how the sourcetype syslog can be configured to take the FQDN of the delivering Universal Forwarder and not to extract the hostname from the log line. &lt;BR /&gt;
Thanks for your help.&lt;/P&gt;</description>
      <pubDate>Sun, 15 May 2011 11:36:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Modify-sourcetype-host-extraction/m-p/102205#M21436</guid>
      <dc:creator>FRoth</dc:creator>
      <dc:date>2011-05-15T11:36:25Z</dc:date>
    </item>
    <item>
      <title>Re: Modify sourcetype host extraction</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Modify-sourcetype-host-extraction/m-p/102206#M21437</link>
      <description>&lt;P&gt;Add the config to props.conf on the &lt;STRONG&gt;indexer&lt;/STRONG&gt;. (See &lt;A href="http://www.splunk.com/wiki/Where_do_I_configure_my_Splunk_settings%3F" target="_blank"&gt;here&lt;/A&gt;, noting that Universal and Light Forwarders work the same way.) This will affect all data with sourcetype &lt;CODE&gt;syslog&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[syslog]
# yes, the next line sets it to an empty value
TRANSFORMS =
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This overrides the default in &lt;CODE&gt;$SPLUNK_HOME/etc/system/default/props.conf&lt;/CODE&gt;, of &lt;CODE&gt;TRANSFORMS = syslog-host&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;There are a few other versions of syslog in the defaults (e.g. cisco_syslog, windows_snare_syslog) that will have their own config that you would have to override separately if you desire.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 09:33:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Modify-sourcetype-host-extraction/m-p/102206#M21437</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2020-09-28T09:33:49Z</dc:date>
    </item>
  </channel>
</rss>

