<?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: Syslog data from UDP. Maximum message size? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-data-from-UDP-Maximum-message-size/m-p/43445#M8090</link>
    <description>&lt;P&gt;Splunk uses the &lt;CODE&gt;TRUNCATE&lt;/CODE&gt; setting in props.conf to determine maximum message size.  By default this is set to 10000 bytes.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;## props.conf.spec
TRUNCATE = &amp;lt;non-negative integer&amp;gt;
* Change the default maximum line length (in bytes).
* Although this is in bytes, line length is rounded down when this would
  otherwise land mid-character for multi-byte characters.
* Set to 0 if you never want truncation (very long lines are, however, often a sign of
  garbage data).
* Defaults to 10000 bytes.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Fri, 15 Jul 2011 18:54:38 GMT</pubDate>
    <dc:creator>hazekamp</dc:creator>
    <dc:date>2011-07-15T18:54:38Z</dc:date>
    <item>
      <title>Syslog data from UDP. Maximum message size?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-data-from-UDP-Maximum-message-size/m-p/43444#M8089</link>
      <description>&lt;P&gt;What's maximum message size which splunk's syslog will accept via UDP? How I can increase it?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jul 2011 10:11:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslog-data-from-UDP-Maximum-message-size/m-p/43444#M8089</guid>
      <dc:creator>eject</dc:creator>
      <dc:date>2011-07-15T10:11:56Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog data from UDP. Maximum message size?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-data-from-UDP-Maximum-message-size/m-p/43445#M8090</link>
      <description>&lt;P&gt;Splunk uses the &lt;CODE&gt;TRUNCATE&lt;/CODE&gt; setting in props.conf to determine maximum message size.  By default this is set to 10000 bytes.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;## props.conf.spec
TRUNCATE = &amp;lt;non-negative integer&amp;gt;
* Change the default maximum line length (in bytes).
* Although this is in bytes, line length is rounded down when this would
  otherwise land mid-character for multi-byte characters.
* Set to 0 if you never want truncation (very long lines are, however, often a sign of
  garbage data).
* Defaults to 10000 bytes.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 15 Jul 2011 18:54:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslog-data-from-UDP-Maximum-message-size/m-p/43445#M8090</guid>
      <dc:creator>hazekamp</dc:creator>
      <dc:date>2011-07-15T18:54:38Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog data from UDP. Maximum message size?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-data-from-UDP-Maximum-message-size/m-p/43446#M8091</link>
      <description>&lt;P&gt;I've set TRUNCATE = 0 in C:\Program Files\Splunk\etc\system\default\props.conf and restarted Splunk. tried to send 2600 bytes and it don't displayed :(. &lt;/P&gt;

&lt;P&gt;With wireshark I see that that messages reached server. &lt;/P&gt;

&lt;P&gt;All messages which are smaller than 1900 bytes displays just fine. How can I debug this problem ?&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jul 2011 10:54:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslog-data-from-UDP-Maximum-message-size/m-p/43446#M8091</guid>
      <dc:creator>eject</dc:creator>
      <dc:date>2011-07-18T10:54:50Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog data from UDP. Maximum message size?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-data-from-UDP-Maximum-message-size/m-p/43447#M8092</link>
      <description>&lt;P&gt;This sounds like a UDP problem, not a splunk problem.&lt;/P&gt;

&lt;P&gt;For me, anything up to 65507 bytes is received (and truncated to 10000 bytes).  Anything longer just gets lost.&lt;/P&gt;

&lt;P&gt;If you have perl, maybe try sending to the following script and seeing what happens:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;my $usage = qq{Usage:
  perl udp_server.pl port
};

use strict;

use IO::Socket;

my $port=shift or die "port not specified\n\n$usage";

my $response = IO::Socket::INET-&amp;gt;new(Proto=&amp;gt;"udp",LocalPort=&amp;gt;$port)
  or die "Can't make UDP server: $@";

my $message=0;

while(1){
  print "Listening on $port...\n";
  my ($datagram,$flags);
  $response-&amp;gt;recv($datagram,100000,$flags) or warn "recv failed: $!\n";
  print "Got message ",++$message," from ", $response-&amp;gt;peerhost,", flags ",$flags || "none",": $datagram\n", "length: ",length $datagram,"\n";
}
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 18 Oct 2013 00:42:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslog-data-from-UDP-Maximum-message-size/m-p/43447#M8092</guid>
      <dc:creator>BenAveling</dc:creator>
      <dc:date>2013-10-18T00:42:23Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog data from UDP. Maximum message size?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-data-from-UDP-Maximum-message-size/m-p/43448#M8093</link>
      <description>&lt;P&gt;I might suggest trying to run strace on splunk's calls to &lt;CODE&gt;recv()&lt;/CODE&gt;.  You'll want to make sure that the buffer size passed to &lt;CODE&gt;recv()&lt;/CODE&gt; is big enough to receive the whole datagram in one call.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2013 02:42:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslog-data-from-UDP-Maximum-message-size/m-p/43448#M8093</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2013-10-18T02:42:30Z</dc:date>
    </item>
  </channel>
</rss>

