<?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: Transaction grouping in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Transaction-grouping/m-p/74772#M18878</link>
    <description>&lt;P&gt;Just a thought, does adding maxspan and maxpause help?&lt;/P&gt;</description>
    <pubDate>Fri, 18 Dec 2015 08:35:11 GMT</pubDate>
    <dc:creator>BenTan</dc:creator>
    <dc:date>2015-12-18T08:35:11Z</dc:date>
    <item>
      <title>Transaction grouping</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transaction-grouping/m-p/74770#M18876</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;I have a transaction which have keyword "start" and "stop", I use startswith and endswith to define the whole transaction, but the problem is the system will detect if it can't finish, it will reload the transaction again, so the log will like:&lt;/P&gt;

&lt;P&gt; start
 action...
 start
 action...
......
 end&lt;/P&gt;

&lt;P&gt;Do someone know how can I get the correct duration between  to ? Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 21 Oct 2010 14:35:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transaction-grouping/m-p/74770#M18876</guid>
      <dc:creator>katalinali</dc:creator>
      <dc:date>2010-10-21T14:35:23Z</dc:date>
    </item>
    <item>
      <title>Re: Transaction grouping</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transaction-grouping/m-p/74771#M18877</link>
      <description>&lt;P&gt;Kat, try to just use only either startswith or endswith. 
e.g. if you see multiple "start" keyword, then one "stop" keyword, you should use 
* | transaction your_field endswith "stop" &lt;/P&gt;</description>
      <pubDate>Thu, 21 Oct 2010 15:14:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transaction-grouping/m-p/74771#M18877</guid>
      <dc:creator>ppang</dc:creator>
      <dc:date>2010-10-21T15:14:51Z</dc:date>
    </item>
    <item>
      <title>Re: Transaction grouping</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transaction-grouping/m-p/74772#M18878</link>
      <description>&lt;P&gt;Just a thought, does adding maxspan and maxpause help?&lt;/P&gt;</description>
      <pubDate>Fri, 18 Dec 2015 08:35:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transaction-grouping/m-p/74772#M18878</guid>
      <dc:creator>BenTan</dc:creator>
      <dc:date>2015-12-18T08:35:11Z</dc:date>
    </item>
    <item>
      <title>Re: Transaction grouping</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transaction-grouping/m-p/74773#M18879</link>
      <description>&lt;P&gt;Remember, in an unsorted Splunk time stream everything is 'backwards' so you might be looking startswith="stop" and endswith="start", as Stop would be the first event it came to.&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2016 16:43:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transaction-grouping/m-p/74773#M18879</guid>
      <dc:creator>kmugglet</dc:creator>
      <dc:date>2016-05-25T16:43:58Z</dc:date>
    </item>
  </channel>
</rss>

