<?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: Using transaction to detect timeouts in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Using-transaction-to-detect-timeouts/m-p/314809#M58941</link>
    <description>&lt;P&gt;Try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Your Base Search Here
|  rex field=_raw "-S:(?&amp;lt;SESSION_ID&amp;gt;\w+)-"
| streamstats time_window=900 min(_time) AS start range(_time) AS duration values(SESSION_ID) dc(SESSION_ID) AS numSessions BY host
| search numSessions&amp;gt;1
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Sun, 03 Sep 2017 00:28:13 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2017-09-03T00:28:13Z</dc:date>
    <item>
      <title>Using transaction to detect timeouts</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-transaction-to-detect-timeouts/m-p/314807#M58939</link>
      <description>&lt;P&gt;I would like to use the transaction command to find adjacent log entries with the same IP and different Session IDs.&lt;BR /&gt;
Ideally, I would only like to return adjacent pairs of log statements with at least a 15 minute timestamp difference between them.&lt;/P&gt;

&lt;P&gt;Here is the REX I'm using to extract SESSION_ID:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;rex field=_raw "-S:(?&amp;lt;SESSION_ID&amp;gt;\w+)-"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Thanks!&lt;BR /&gt;
Jonathan&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2017 17:35:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-transaction-to-detect-timeouts/m-p/314807#M58939</guid>
      <dc:creator>jbrenner</dc:creator>
      <dc:date>2017-08-31T17:35:00Z</dc:date>
    </item>
    <item>
      <title>Re: Using transaction to detect timeouts</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-transaction-to-detect-timeouts/m-p/314808#M58940</link>
      <description>&lt;P&gt;some examples of your data would be helpful. transaction will only allow you to put in arguments for max pause, though you could search for durations after the fact. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|transaction IP SESSION_ID maxevents=2|search duration&amp;gt;=900
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/6.6.1/SearchReference/Transaction"&gt;https://docs.splunk.com/Documentation/SplunkCloud/6.6.1/SearchReference/Transaction&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;i prefer streamstats, myself.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|sort 0 IP SESSION_ID + _time
| streamstats window=1 current=f values(_time) as previousTime by IP SESSION_ID|eval duration=_time-previousTime|search duration&amp;gt;=900
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/SplunkCloud/6.6.1/SearchReference/Streamstats"&gt;http://docs.splunk.com/Documentation/SplunkCloud/6.6.1/SearchReference/Streamstats&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;just for ideas.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2017 19:12:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-transaction-to-detect-timeouts/m-p/314808#M58940</guid>
      <dc:creator>cmerriman</dc:creator>
      <dc:date>2017-08-31T19:12:58Z</dc:date>
    </item>
    <item>
      <title>Re: Using transaction to detect timeouts</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-transaction-to-detect-timeouts/m-p/314809#M58941</link>
      <description>&lt;P&gt;Try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Your Base Search Here
|  rex field=_raw "-S:(?&amp;lt;SESSION_ID&amp;gt;\w+)-"
| streamstats time_window=900 min(_time) AS start range(_time) AS duration values(SESSION_ID) dc(SESSION_ID) AS numSessions BY host
| search numSessions&amp;gt;1
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sun, 03 Sep 2017 00:28:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-transaction-to-detect-timeouts/m-p/314809#M58941</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-09-03T00:28:13Z</dc:date>
    </item>
  </channel>
</rss>

