<?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 How can I avoid from adding an original hostname(or, IP address) to _SYSLOG_ROUGING event when forwarding a third party server? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-avoid-from-adding-an-original-hostname-or-IP-address/m-p/441008#M76874</link>
    <description>&lt;P&gt;How can I avoid from adding an original hostname(or, IP address) to _SYSLOG_ROUGING event when forwarding a third party server?  &lt;/P&gt;

&lt;P&gt;I can see that  Splunk add host information to original syslog event when using _SYSLOG_ROUTING to forward syslog events to a third party server?  &lt;/P&gt;

&lt;P&gt;Below is an example added the server's IP address 192.168.10.111 which was already in the original event.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;192.168.10.111 Mar 16 00:01:29 192.168.10.111 postfix/qmgr[1106]: EA11004022: from=, size=3514, nrcpt=1 (queue active) 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;How can I remove the host name? &lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 23:03:12 GMT</pubDate>
    <dc:creator>Masa</dc:creator>
    <dc:date>2020-09-29T23:03:12Z</dc:date>
    <item>
      <title>How can I avoid from adding an original hostname(or, IP address) to _SYSLOG_ROUGING event when forwarding a third party server?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-avoid-from-adding-an-original-hostname-or-IP-address/m-p/441008#M76874</link>
      <description>&lt;P&gt;How can I avoid from adding an original hostname(or, IP address) to _SYSLOG_ROUGING event when forwarding a third party server?  &lt;/P&gt;

&lt;P&gt;I can see that  Splunk add host information to original syslog event when using _SYSLOG_ROUTING to forward syslog events to a third party server?  &lt;/P&gt;

&lt;P&gt;Below is an example added the server's IP address 192.168.10.111 which was already in the original event.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;192.168.10.111 Mar 16 00:01:29 192.168.10.111 postfix/qmgr[1106]: EA11004022: from=, size=3514, nrcpt=1 (queue active) 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;How can I remove the host name? &lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 23:03:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-I-avoid-from-adding-an-original-hostname-or-IP-address/m-p/441008#M76874</guid>
      <dc:creator>Masa</dc:creator>
      <dc:date>2020-09-29T23:03:12Z</dc:date>
    </item>
    <item>
      <title>Re: How can I avoid from adding an original hostname(or, IP address) to _SYSLOG_ROUGING event when forwarding a third party server?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-avoid-from-adding-an-original-hostname-or-IP-address/m-p/441009#M76875</link>
      <description>&lt;P&gt;Probably you're using non-syslog sourcetype. In that case, try &lt;STRONG&gt;syslogSourceType&lt;/STRONG&gt; attribute in outputs.conf. This should avoid adding the originated hostname. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;syslogSourceType = &amp;lt;string&amp;gt;
* Specifies an additional rule for handling data, in addition to that 
  provided by the 'syslog' source type.
* This string is used as a substring match against the sourcetype key. For
  example, if the string is set to "syslog", then all sourcetypes
  containing the string 'syslog' receive this special treatment.
* To match a sourcetype explicitly, use the pattern
  "sourcetype::sourcetype_name".
    * Example: syslogSourceType = sourcetype::apache_common
* Data that is "syslog" or matches this setting is assumed to already be in 
  syslog format. 
* Data that does not match the rules has a header, optionally a timestamp 
  (if defined in 'timestampformat'), and a hostname added to the front of 
  the event. This is how Splunk software causes arbitrary log data to match syslog expectations.
* No default.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;For more detail, &lt;BR /&gt;
Official Doc:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Data/HowSplunkEnterprisehandlessyslogdata"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Data/HowSplunkEnterprisehandlessyslogdata&lt;/A&gt;&lt;BR /&gt;
Community Wiki: (old)&lt;BR /&gt;
&lt;A href="https://wiki.splunk.com/Community:Test:How_Splunk_behaves_when_receiving_or_forwarding_udp_data"&gt;https://wiki.splunk.com/Community:Test:How_Splunk_behaves_when_receiving_or_forwarding_udp_data&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/6482i396A982143B2AEC7/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jan 2019 23:09:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-I-avoid-from-adding-an-original-hostname-or-IP-address/m-p/441009#M76875</guid>
      <dc:creator>Masa</dc:creator>
      <dc:date>2019-01-31T23:09:43Z</dc:date>
    </item>
  </channel>
</rss>

