<?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: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340925#M166064</link>
    <description>&lt;P&gt;Hi everybody&lt;/P&gt;

&lt;P&gt;After extensive research &amp;amp; self learning about the capabilities &amp;amp; limitations splunk, this is not feasible.&lt;BR /&gt;
I have opted to use Protocol Data Input app.&lt;BR /&gt;
Using Module Inputs I have managed to get the results.&lt;/P&gt;

&lt;P&gt;Again thank  you everyone for your support and answers.&lt;/P&gt;

&lt;P&gt;Pinaki&lt;/P&gt;</description>
    <pubDate>Sun, 05 Nov 2017 20:18:04 GMT</pubDate>
    <dc:creator>pinakicybermak</dc:creator>
    <dc:date>2017-11-05T20:18:04Z</dc:date>
    <item>
      <title>Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340912#M166051</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;

&lt;P&gt;I am using splunk stream. Packet stream to capture data from source and destination content fields.&lt;BR /&gt;
For a persistent TCP connection i just cannot seem to break/split in separate events or lines.&lt;BR /&gt;
Is there no way to so this?&lt;BR /&gt;
Other advice appreciated.&lt;BR /&gt;
I am willing to check other alternatives, willing to truncate the data, etc etc etc&lt;/P&gt;

&lt;P&gt;Sample event Single TCP Conn Open/Close &lt;BR /&gt;
{"endtime":"2017-09-17T15:30:47.271015Z","timestamp":"2017-09-17T15:30:36.440073Z","ack_packets_in":4,"ack_packets_out":5,"app":"tcp","bytes":645,"bytes_in":353,"bytes_out":292,"client_rtt":16,"client_rtt_packets":1,"client_rtt_sum":16,"connection":"192.168.100.3:65534","data_packets_in":1,"data_packets_out":0,"dest_ip":"192.168.100.3","dest_port":65534,"duplicate_packets_in":0,"duplicate_packets_out":0,"missing_packets_in":0,"missing_packets_out":0,"network_interface":"lo0","packets_in":6,"packets_out":5,"protocol_stack":"ip:tcp:unknown","server_rtt":40,"server_rtt_packets":2,"server_rtt_sum":81,"src_ip":"192.168.100.3","src_port":51448,"tcp_status":0,"time_taken":10830958,"SRCCNT":"68656c6c6f"}&lt;/P&gt;

&lt;P&gt;Sample Event TCP persistent Stream&lt;BR /&gt;
{"endtime":"2017-09-17T15:32:06.278243Z","timestamp":"2017-09-17T15:30:57.342570Z","ack_packets_in":3,"ack_packets_out":158,"app":"tcp","bytes":18484,"bytes_in":9624,"bytes_out":8860,"client_rtt":14,"client_rtt_packets":1,"client_rtt_sum":14,"connection":"192.168.100.3:65534","data_packets_in":153,"data_packets_out":0,"dest_ip":"192.168.100.3","dest_port":65534,"duplicate_packets_in":0,"duplicate_packets_out":0,"missing_packets_in":0,"missing_packets_out":0,"network_interface":"lo0","packets_in":157,"packets_out":158,"protocol_stack":"ip:tcp:unknown","server_rtt":33,"server_rtt_packets":154,"server_rtt_sum":5226,"src_ip":"192.168.100.3","src_port":51475,"tcp_status":0,"time_taken":68935687,"SRCCNT":"68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f"}&lt;/P&gt;

&lt;P&gt;I need the above stream to be broken up into separate events. Sorta like a wireshark view&lt;/P&gt;

&lt;P&gt;Thank You &amp;amp; appreciate any and all ideas/assistance.&lt;BR /&gt;
Pinaki&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 15:48:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340912#M166051</guid>
      <dc:creator>pinakicybermak</dc:creator>
      <dc:date>2020-09-29T15:48:03Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340913#M166052</link>
      <description>&lt;P&gt;If the above is not at all possible, kindly let me know. I will choose alternate methods. Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 17 Sep 2017 18:40:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340913#M166052</guid>
      <dc:creator>pinakicybermak</dc:creator>
      <dc:date>2017-09-17T18:40:46Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340914#M166053</link>
      <description>&lt;P&gt;not clear what you want...I need the above stream to be broken up into separate events. Sorta like a wireshark view??&lt;BR /&gt;
Can you give a sample of how you would like the events to be broken up into?&lt;/P&gt;</description>
      <pubDate>Mon, 18 Sep 2017 09:42:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340914#M166053</guid>
      <dc:creator>Sukisen1981</dc:creator>
      <dc:date>2017-09-18T09:42:07Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340915#M166054</link>
      <description>&lt;P&gt;So let me clarify my objective - I am concerned only with the data i.e. src &amp;amp; dest content (extracted data field SRCCNT) with couple of other fields like RTT , dest/src ip/port timestamp etc.&lt;BR /&gt;
In splunk stream - TCP persistent connection all the data values club together and the SRCCNT becomes a huge bulk field (due to TCPreassembly at the splunk) and I cannot work with the data. I ultimately need the data to be shown as below - Each as a Single Event&lt;/P&gt;

&lt;P&gt;{"endtime":"2017-09-17T15:30:47.271015Z","timestamp":"2017-09-17T15:30:36.440073Z","ack_packets_in":4,"ack_packets_out":5,"app":"tcp","bytes":645,"bytes_in":353,"bytes_out":292,"client_rtt":16,"client_rtt_packets":1,"client_rtt_sum":16,"connection":"192.168.100.3:65534","data_packets_in":1,"data_packets_out":0,"dest_ip":"192.168.100.3","dest_port":65534,"duplicate_packets_in":0,"duplicate_packets_out":0,"missing_packets_in":0,"missing_packets_out":0,"network_interface":"lo0","packets_in":6,"packets_out":5,"protocol_stack":"ip:tcp:unknown","server_rtt":40,"server_rtt_packets":2,"server_rtt_sum":81,"src_ip":"192.168.100.3","src_port":51448,"tcp_status":0,"time_taken":10830958,"SRCCNT":"68656c6c6f"}&lt;BR /&gt;
&lt;IMG src="https://community.splunk.com/storage/temp/216573-wireshark.png" alt="alt text" /&gt;&lt;BR /&gt;
Thanx&lt;BR /&gt;
Pinaki&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 15:48:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340915#M166054</guid>
      <dc:creator>pinakicybermak</dc:creator>
      <dc:date>2020-09-29T15:48:40Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340916#M166055</link>
      <description>&lt;P&gt;I am sorry , is till can not figure this out. You have 49391 in your sample 'would be' event but I can not see that number anywhere in your raw event, where is this number coming from? Also you have 61 , 56 etc, in your screen shot , I can not see them anywhere in your raw event...&lt;/P&gt;</description>
      <pubDate>Mon, 18 Sep 2017 17:57:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340916#M166055</guid>
      <dc:creator>Sukisen1981</dc:creator>
      <dc:date>2017-09-18T17:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340917#M166056</link>
      <description>&lt;P&gt;Hi Suki,&lt;/P&gt;

&lt;P&gt;The above are just samples. 49391 is the port. 61/56 are the bytes. This is Wireshark.&lt;BR /&gt;
This is TCP PERSISTENT Stream. TCP PERSISTENT Stream is a TCP connection is always in connected state till Closure by either client/server.&lt;/P&gt;

&lt;P&gt;You can see this value in the pic? - 68656c6c6f. In a single TCP OPEN/Close this comes as 1 event in splunk. &lt;/P&gt;

&lt;P&gt;However in a Persistent stream this become "68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f" in splunk. I want the similar line event view in splunk as shown in the wireshark image. This is the value I want in single line for TCP PERSISTENT Stream.&lt;/P&gt;

&lt;P&gt;So hence "68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f68656c6c6f" should be broken in separate lines with supporting data&lt;BR /&gt;
e.g. events&lt;BR /&gt;
68656c6c6f&lt;BR /&gt;
68656c6c6f&lt;BR /&gt;
68656c6c6f&lt;BR /&gt;
68656c6c6f&lt;BR /&gt;
68656c6c6f&lt;BR /&gt;
68656c6c6f&lt;BR /&gt;
68656c6c6f&lt;BR /&gt;
68656c6c6f&lt;BR /&gt;
68656c6c6f&lt;BR /&gt;
68656c6c6f&lt;/P&gt;

&lt;P&gt;hope the above clarifies your question. I just need to know if possible or not. If possible how. Thank you for your help.&lt;BR /&gt;
Pinaki&lt;/P&gt;</description>
      <pubDate>Tue, 19 Sep 2017 16:58:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340917#M166056</guid>
      <dc:creator>pinakicybermak</dc:creator>
      <dc:date>2017-09-19T16:58:13Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340918#M166057</link>
      <description>&lt;P&gt;Hey @sukisen1981, thank you so much for contributing to Splunk Answers! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Please remember to press "add comment" instead of "add answer" when it's part of discussion. (I just converted this answer post to a comment.) &lt;/P&gt;</description>
      <pubDate>Tue, 19 Sep 2017 17:04:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340918#M166057</guid>
      <dc:creator>lfedak_splunk</dc:creator>
      <dc:date>2017-09-19T17:04:13Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340919#M166058</link>
      <description>&lt;P&gt;@pinakicybermak - are all the SRCCNT values identical in length, or is there another way to distinguish where one ends and the next begins?&lt;/P&gt;</description>
      <pubDate>Fri, 29 Sep 2017 14:50:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340919#M166058</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-09-29T14:50:50Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340920#M166059</link>
      <description>&lt;P&gt;Dear Dal,&lt;/P&gt;

&lt;P&gt;SRCCNT values - Not identical.&lt;BR /&gt;
SRCCNT values extracted from either dest_content/src_content in hex&lt;BR /&gt;
no distinguishing start/end&lt;BR /&gt;
for example 1 hex full packet maybe&lt;BR /&gt;
"00ac00ef384eeee000000100ac00ef384eeee0000020000000ac00ef384eeee&amp;lt;128Bytes of data&amp;gt;&amp;lt;128bytes&amp;gt;"&lt;BR /&gt;
2nd packet may be&lt;BR /&gt;
"00ac00ef2343234000000100ac00ef23432340000020000000ac00ef2343234&amp;lt;128Bytes of data&amp;gt;&amp;lt;128bytes&amp;gt;"&lt;BR /&gt;
3rd packet maybe&lt;BR /&gt;
"00ab00ef1234000000100ab00ef12340000020000000ab00ef1234&amp;lt;128Bytes of data&amp;gt;&amp;lt;128bytes&amp;gt;"&lt;BR /&gt;
I am actually trying to parse ISO8583 msg which comes in hex. I am successful if the data is coming with 1 tcp open/close. When it comes in stream it looks like &lt;BR /&gt;
SRCCNT = 00ac00ef384eeee000000100ac00ef384eeee0000020000000ac00ef384eeee&amp;lt;128Bytes of data&amp;gt;&amp;lt;128bytes&amp;gt;00ac00ef2343234000000100ac00ef23432340000020000000ac00ef2343234&amp;lt;128Bytes of data&amp;gt;&amp;lt;128bytes&amp;gt;00ab00ef1234000000100ab00ef12340000020000000ab00ef1234&amp;lt;128Bytes of data&amp;gt;&amp;lt;128bytes&amp;gt;&lt;/P&gt;

&lt;P&gt;Thank You&lt;BR /&gt;
Pinaki&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 16:04:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340920#M166059</guid>
      <dc:creator>pinakicybermak</dc:creator>
      <dc:date>2020-09-29T16:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340921#M166060</link>
      <description>&lt;P&gt;Pinaki,&lt;/P&gt;

&lt;P&gt;If I am reading this right, your problem is that Splunk/Stream reassembled the packets in a TCP flow, but you want to see the raw individual packets that made up that flow?&lt;/P&gt;

&lt;P&gt;Have you tried faking it out by setting &lt;CODE&gt;maxTcpReassemblyPacketCount&lt;/CODE&gt; in &lt;A href="http://docs.splunk.com/Documentation/StreamApp/7.1.1/DeployStreamApp/ConfigureStreamForwarder"&gt;streamfwd.conf&lt;/A&gt; to &lt;CODE&gt;1&lt;/CODE&gt; instead of the default 500000?&lt;/P&gt;

&lt;P&gt;I do NOT know if that will work - well, I know it should work but I don't know if it will work &lt;EM&gt;usefully.&lt;/EM&gt;  It could very well just make a mess of things.  &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Give that a try, though, and report back.  If that does the trick I would be happy to convert this to an answer so you can accept it.  If it does not, well, it may be a useful comment/trick for the next person who stumbles across this question.  &lt;/P&gt;

&lt;P&gt;Happy Splunking!&lt;BR /&gt;
-Rich&lt;/P&gt;</description>
      <pubDate>Tue, 03 Oct 2017 11:15:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340921#M166060</guid>
      <dc:creator>Richfez</dc:creator>
      <dc:date>2017-10-03T11:15:16Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340922#M166061</link>
      <description>&lt;P&gt;Dear Rich,&lt;/P&gt;

&lt;P&gt;Thank you for your reply. Yes i have already tried that. It does work, but again not a perfect solution. If i could configure that to "ms" instead of "sec" the result would be better.&lt;/P&gt;

&lt;P&gt;Thank You&lt;BR /&gt;
Pinaki Banerjee&lt;/P&gt;</description>
      <pubDate>Thu, 05 Oct 2017 18:51:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340922#M166061</guid>
      <dc:creator>pinakicybermak</dc:creator>
      <dc:date>2017-10-05T18:51:24Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340923#M166062</link>
      <description>&lt;P&gt;When  you say if you could configure that to "ms" instead of seconds, are you talking about the timestamp that Splunk is using isn't using the full precision available?  That might be fixable.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Oct 2017 19:03:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340923#M166062</guid>
      <dc:creator>Richfez</dc:creator>
      <dc:date>2017-10-05T19:03:14Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340924#M166063</link>
      <description>&lt;P&gt;Dear Rich,&lt;/P&gt;

&lt;P&gt;Clarification and apologies. I used the tcpConnectionTimeout  (lowest value 1 sec) to almost solve the problem but I faced scenarios where I got multiple transactions with 1 sec.&lt;BR /&gt;
I also used maxTcpReassemblyPacketCount = 1 but i was getting 2 records always.&lt;/P&gt;

&lt;P&gt;If I have understood your comment correctly - "ms", "full precision" - This is an idea i havent tried. If this is doable then maybe it will break with full precision timestamp and i may get all the records including the breakdown handshakes etc. I want to try. Can you give me how to do it?&lt;/P&gt;

&lt;P&gt;Thank You&lt;BR /&gt;
Pinaki&lt;/P&gt;</description>
      <pubDate>Sat, 07 Oct 2017 06:53:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340924#M166063</guid>
      <dc:creator>pinakicybermak</dc:creator>
      <dc:date>2017-10-07T06:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Stream split separate events for persistent tcp stream or Disable TCPREASSEMBLY or some other method</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340925#M166064</link>
      <description>&lt;P&gt;Hi everybody&lt;/P&gt;

&lt;P&gt;After extensive research &amp;amp; self learning about the capabilities &amp;amp; limitations splunk, this is not feasible.&lt;BR /&gt;
I have opted to use Protocol Data Input app.&lt;BR /&gt;
Using Module Inputs I have managed to get the results.&lt;/P&gt;

&lt;P&gt;Again thank  you everyone for your support and answers.&lt;/P&gt;

&lt;P&gt;Pinaki&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2017 20:18:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Stream-split-separate-events-for-persistent-tcp-stream-or/m-p/340925#M166064</guid>
      <dc:creator>pinakicybermak</dc:creator>
      <dc:date>2017-11-05T20:18:04Z</dc:date>
    </item>
  </channel>
</rss>

