<?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: Parsing logs from UDP input in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-logs-from-UDP-input/m-p/347281#M93833</link>
    <description>&lt;P&gt;There are multiple options. &lt;BR /&gt;
1. You can update  stanza to listen for UDP traffic on port 514. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[udp://2514]
sourcetype = Your Sourcetype
index= Define it if it's other than main
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;OL&gt;
&lt;LI&gt;&lt;P&gt;Use syslogd/rsyslogd to listen for UDP traffic on port 514 and then put those contents into file which will be read by Splunk. You can keep your inputs.conf configuration as is and configure syslogd to put logs into the same file for which you have input configuration. Sample configuration is as follows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;$ModLoad imudp
$UDPServerRun 514
### Put logs to file ###
$template rtflow,"$YOURFILELOCATION"
if $msg contains 'RT_FLOW' then -?rtflow
&amp;amp; ~
&lt;/CODE&gt;&lt;/PRE&gt;&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;I would prefer second option as the chance of data loss is reduced in case of Splunk server is restarted.&lt;/P&gt;</description>
    <pubDate>Wed, 01 Nov 2017 05:25:43 GMT</pubDate>
    <dc:creator>hardikJsheth</dc:creator>
    <dc:date>2017-11-01T05:25:43Z</dc:date>
    <item>
      <title>Parsing logs from UDP input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-logs-from-UDP-input/m-p/347280#M93832</link>
      <description>&lt;P&gt;I installed addon for my product but the problem is that the addon is intended to collect data from the file, and not from receiving at udp 514 port. How should I reconfigure conf files to make it work?&lt;/P&gt;</description>
      <pubDate>Wed, 01 Nov 2017 01:48:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-logs-from-UDP-input/m-p/347280#M93832</guid>
      <dc:creator>test_qweqwe</dc:creator>
      <dc:date>2017-11-01T01:48:03Z</dc:date>
    </item>
    <item>
      <title>Re: Parsing logs from UDP input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-logs-from-UDP-input/m-p/347281#M93833</link>
      <description>&lt;P&gt;There are multiple options. &lt;BR /&gt;
1. You can update  stanza to listen for UDP traffic on port 514. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[udp://2514]
sourcetype = Your Sourcetype
index= Define it if it's other than main
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;OL&gt;
&lt;LI&gt;&lt;P&gt;Use syslogd/rsyslogd to listen for UDP traffic on port 514 and then put those contents into file which will be read by Splunk. You can keep your inputs.conf configuration as is and configure syslogd to put logs into the same file for which you have input configuration. Sample configuration is as follows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;$ModLoad imudp
$UDPServerRun 514
### Put logs to file ###
$template rtflow,"$YOURFILELOCATION"
if $msg contains 'RT_FLOW' then -?rtflow
&amp;amp; ~
&lt;/CODE&gt;&lt;/PRE&gt;&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;I would prefer second option as the chance of data loss is reduced in case of Splunk server is restarted.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Nov 2017 05:25:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-logs-from-UDP-input/m-p/347281#M93833</guid>
      <dc:creator>hardikJsheth</dc:creator>
      <dc:date>2017-11-01T05:25:43Z</dc:date>
    </item>
  </channel>
</rss>

