<?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 Lost packages when using tcp syslog and packages need to be splitted because of big size in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Lost-packages-when-using-tcp-syslog-and-packages-need-to-be/m-p/505941#M86184</link>
    <description>&lt;P&gt;When using syslog through tcp (instead of udp) from imperva, many packages are lost since they do not arrive in order. So at destination everything is screwed up since they can not be reassembled&lt;/P&gt;</description>
    <pubDate>Wed, 24 Jun 2020 11:34:50 GMT</pubDate>
    <dc:creator>leebsr</dc:creator>
    <dc:date>2020-06-24T11:34:50Z</dc:date>
    <item>
      <title>Lost packages when using tcp syslog and packages need to be splitted because of big size</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Lost-packages-when-using-tcp-syslog-and-packages-need-to-be/m-p/505941#M86184</link>
      <description>&lt;P&gt;When using syslog through tcp (instead of udp) from imperva, many packages are lost since they do not arrive in order. So at destination everything is screwed up since they can not be reassembled&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jun 2020 11:34:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Lost-packages-when-using-tcp-syslog-and-packages-need-to-be/m-p/505941#M86184</guid>
      <dc:creator>leebsr</dc:creator>
      <dc:date>2020-06-24T11:34:50Z</dc:date>
    </item>
  </channel>
</rss>

