<?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 Why are my udp syslog input events getting merged? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10572#M374</link>
    <description>&lt;P&gt;Odd behaviour with some udp syslog input from a Panorama device (palo alto management device)
and ArcSight connector using the same udp input port.
Input settings as follows&lt;/P&gt;

&lt;P&gt;[udp://515]&lt;BR /&gt;
disabled = false&lt;BR /&gt;
sourcetype = threat_events&lt;BR /&gt;
index = myindex  &lt;/P&gt;

&lt;P&gt;props.conf&lt;BR /&gt;
[sourcetype::threat_events]&lt;BR /&gt;
TZ = UTC&lt;BR /&gt;
SHOULD_LINEMERGE = False  &lt;/P&gt;

&lt;P&gt;Linemerge settings were set to false for the sourcetype as seen above, however events merged at together sometimes. Is this an example of getting the right LINE_BREAKER= correct for the device? &lt;/P&gt;</description>
    <pubDate>Fri, 26 Mar 2010 05:31:08 GMT</pubDate>
    <dc:creator>Chris_R_</dc:creator>
    <dc:date>2010-03-26T05:31:08Z</dc:date>
    <item>
      <title>Why are my udp syslog input events getting merged?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10572#M374</link>
      <description>&lt;P&gt;Odd behaviour with some udp syslog input from a Panorama device (palo alto management device)
and ArcSight connector using the same udp input port.
Input settings as follows&lt;/P&gt;

&lt;P&gt;[udp://515]&lt;BR /&gt;
disabled = false&lt;BR /&gt;
sourcetype = threat_events&lt;BR /&gt;
index = myindex  &lt;/P&gt;

&lt;P&gt;props.conf&lt;BR /&gt;
[sourcetype::threat_events]&lt;BR /&gt;
TZ = UTC&lt;BR /&gt;
SHOULD_LINEMERGE = False  &lt;/P&gt;

&lt;P&gt;Linemerge settings were set to false for the sourcetype as seen above, however events merged at together sometimes. Is this an example of getting the right LINE_BREAKER= correct for the device? &lt;/P&gt;</description>
      <pubDate>Fri, 26 Mar 2010 05:31:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10572#M374</guid>
      <dc:creator>Chris_R_</dc:creator>
      <dc:date>2010-03-26T05:31:08Z</dc:date>
    </item>
    <item>
      <title>Re: Why are my udp syslog input events getting merged?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10573#M375</link>
      <description>&lt;P&gt;One workaround was to use separate network ports for the different devices, curious to hear the answer though.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Mar 2010 05:32:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10573#M375</guid>
      <dc:creator>Chris_R_</dc:creator>
      <dc:date>2010-03-26T05:32:34Z</dc:date>
    </item>
    <item>
      <title>Re: Why are my udp syslog input events getting merged?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10574#M376</link>
      <description>&lt;P&gt;Probably. &lt;CODE&gt;LINE_BREAKER&lt;/CODE&gt; by default is &lt;CODE&gt;([\r\n]+)&lt;/CODE&gt;, that is, any sequence of newlines and carriage returns. In addition, the end of a UDP packet will also end an event. It's not clear to my why you would have merged events in this case. Was there any pattern or commonality to the merged events?&lt;/P&gt;</description>
      <pubDate>Fri, 26 Mar 2010 09:30:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10574#M376</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-03-26T09:30:53Z</dc:date>
    </item>
    <item>
      <title>Re: Why are my udp syslog input events getting merged?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10575#M377</link>
      <description>&lt;P&gt;They were getting merged events where a arcsight event would come through and multiple panorama event (starting with CEF) would get merged one after another ( client info removed )&lt;/P&gt;

&lt;P&gt;Mar 4 18:47:25 somehost.com Mar 4 18:48:06 1,2010/03/048:48:06,0004A100609,THREAT,url,46,2010/03/04 18:48:05,10.170.133.122,82.195.186.201,0.0.0.0,0.0.0.0,ProxyAccess-A2,,,web-browsing,xtxs1,Int-FW,Int-FW-Proxy blah....de....blah....informational,0  (&amp;lt;---first event should end here)&lt;BR /&gt;
CEF:0|Palo Alto|Panorama|||THREAT|Unknown| eventId=1428238 proto=UDP art=1267728483290 rt=1267728481000 shost=somehost.com src=10.97.3.55 sourceZoneURI=/zzz Zones/System Zones/Private Address Space dst=22.11.22.33 blah ....de...blah...dtz=Asia/xyz deviceFacility=IPS  (&amp;lt;--- Second event should end here)&lt;BR /&gt;
CEF:0|Palo Alto|Panorama (&amp;lt;---they continued to get multiple CEF Panorama device events all merged with the above)&lt;/P&gt;</description>
      <pubDate>Fri, 26 Mar 2010 23:57:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10575#M377</guid>
      <dc:creator>Chris_R_</dc:creator>
      <dc:date>2010-03-26T23:57:02Z</dc:date>
    </item>
    <item>
      <title>Re: Why are my udp syslog input events getting merged?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10576#M378</link>
      <description>&lt;P&gt;look to me then that &lt;CODE&gt;SHOULD_LINEMERGE = false&lt;/CODE&gt; wasn't taking effect. (And therefore default &lt;CODE&gt;BREAK_ONLY_BEFORE_DATE = true&lt;/CODE&gt; was in effect.) I always use lower-case &lt;CODE&gt;false&lt;/CODE&gt; instead of upper-case &lt;CODE&gt;False&lt;/CODE&gt;. I have no idea if that makes a difference.&lt;/P&gt;</description>
      <pubDate>Sat, 10 Apr 2010 23:21:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10576#M378</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-04-10T23:21:50Z</dc:date>
    </item>
    <item>
      <title>Re: Why are my udp syslog input events getting merged?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10577#M379</link>
      <description>&lt;P&gt;Use a stanza name:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[threat_events]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;not&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[sourcetype::threat_events]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We don't have any support for that syntax, and it shouldn't be in the docs anywhere (I can see how you might think there would be, of course).&lt;/P&gt;

&lt;P&gt;Thus you should have:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[threat_events]
TZ = UTC
SHOULD_LINEMERGE = False 
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 17 Apr 2010 07:20:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-my-udp-syslog-input-events-getting-merged/m-p/10577#M379</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2010-04-17T07:20:55Z</dc:date>
    </item>
  </channel>
</rss>

