<?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: Transactions within transactions in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39340#M8971</link>
    <description>&lt;P&gt;AFAICT from the logs, and because I am doing a transaction based upon the RID, the connect is just the next sequential step after the DAO START.&lt;/P&gt;</description>
    <pubDate>Mon, 19 Aug 2013 18:45:57 GMT</pubDate>
    <dc:creator>tyronetv</dc:creator>
    <dc:date>2013-08-19T18:45:57Z</dc:date>
    <item>
      <title>Transactions within transactions</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39338#M8969</link>
      <description>&lt;P&gt;I have a set of two logs that share a common field (RID).  One log contains the "user" actions while the other log contains the java, odbc, etc., actions (ibatis log).&lt;/P&gt;

&lt;P&gt;What I need to do, is figure out if there is a delay between when a user makes a request and the actual connection to the database. &lt;/P&gt;

&lt;P&gt;2013-08-19 06:40:32,904 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 c.r.t.r.o.service.OnlineDecisioning - &amp;lt;DAO CALL START&amp;gt;   {USER ID} null  {DAO PROCEDURE} OnlineDecisioning.getTransactionDetails  {INPUT PARAMS} {transactionid=2404611298, callinguserid=-5710326788253269740}&lt;/P&gt;

&lt;P&gt;2013-08-19 06:40:32,908 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 java.sql.Connection - {conn-473946} Connection&lt;/P&gt;

&lt;P&gt;... some other actions .....&lt;/P&gt;

&lt;P&gt;2013-08-19 06:40:33,332 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 c.r.t.r.o.service.OnlineDecisioning - &amp;lt;DAO CALL START&amp;gt;    {USER ID} null  {DAO PROCEDURE} OnlineDecisioning.lockTransaction  {INPUT PARAMS} {transactionid=2404611298, latestchangeid=449327573, callinguserid=-5710326788253269740}&lt;/P&gt;

&lt;P&gt;2013-08-19 06:40:33,333 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 java.sql.Connection - {conn-473948} Connection&lt;/P&gt;

&lt;P&gt;...some other actions....&lt;/P&gt;

&lt;P&gt;2013-08-19 06:45:06,130 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 c.r.t.r.o.service.OnlineDecisioning - &amp;lt;DAO CALL START&amp;gt;    {USER ID} null  {DAO PROCEDURE} OnlineDecisioning.getCouponFieldMappings  {INPUT PARAMS} {documentTypeId=2642998, callinguserid=-5710326788253269740}&lt;/P&gt;

&lt;P&gt;2013-08-19 06:45:06,130 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 java.sql.Connection - {conn-486974} Connection&lt;/P&gt;

&lt;P&gt;... and other various versions of this....&lt;/P&gt;

&lt;P&gt;2013-08-19 06:40:32,904 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 c.r.t.r.o.service.OnlineDecisioning - &amp;lt;DAO CALL START&amp;gt;    {USER ID} null  {DAO PROCEDURE} OnlineDecisioning.getTransactionDetails  {INPUT PARAMS} {transactionid=2404611298, callinguserid=-5710326788253269740}&lt;/P&gt;

&lt;P&gt;2013-08-19 06:40:32,908 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 java.sql.Connection - {conn-473946} Connection&lt;/P&gt;

&lt;P&gt;... some other actions .....&lt;/P&gt;

&lt;P&gt;2013-08-19 06:40:33,332 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 c.r.t.r.o.service.OnlineDecisioning - &amp;lt;DAO CALL START&amp;gt;    {USER ID} null  {DAO PROCEDURE} OnlineDecisioning.lockTransaction  {INPUT PARAMS} {transactionid=2404611298, latestchangeid=449327573, callinguserid=-5710326788253269740}&lt;/P&gt;

&lt;P&gt;2013-08-19 06:40:33,333 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 java.sql.Connection - {conn-473948} Connection&lt;/P&gt;

&lt;P&gt;...some other actions....&lt;/P&gt;

&lt;P&gt;2013-08-19 06:45:06,130 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 c.r.t.r.o.service.OnlineDecisioning -&amp;lt;DAO CALL START&amp;gt;    {USER ID} null  {DAO PROCEDURE} OnlineDecisioning.getCouponFieldMappings  {INPUT PARAMS} {documentTypeId=2642998, callinguserid=-5710326788253269740}&lt;/P&gt;

&lt;P&gt;2013-08-19 06:45:06,130 DEBUG [andler-RMICallHandler-192] RID=1376919632894-63948 java.sql.Connection - {conn-486974} Connection&lt;/P&gt;

&lt;P&gt;... and other various versions of this....&lt;/P&gt;

&lt;P&gt;As you can see, the connection is VERY fast.  Unfortunately, sometimes, it is not.  When it is NOT we have a problem that is about ready to increase exponentially and cause some pain for our customers and, well, me.&lt;/P&gt;

&lt;P&gt;What I want to do is put in place a 'real time' monitor that says the time between the line with &amp;lt;DAO CALL START&amp;gt; in a sourcetype of t2_app and the java.sql.Connection in the sourcetype of ibatis cant exceed X seconds or milliseconds.  (And, also to be able to graph normal response times.)&lt;/P&gt;

&lt;P&gt;I can do a &amp;lt;DAO START&amp;gt; to a &amp;lt;DAO COMPLETE&amp;gt; but that is too much. Just need to know from start to DB connect.&lt;/P&gt;

&lt;P&gt;Suggestions?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2013 18:30:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39338#M8969</guid>
      <dc:creator>tyronetv</dc:creator>
      <dc:date>2013-08-19T18:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: Transactions within transactions</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39339#M8970</link>
      <description>&lt;P&gt;How do you relate the db connection to a particular DAO START message? Or is it always sequential so you can count on that the first connection following DAO START is the connection that's related to it?&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2013 18:36:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39339#M8970</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-08-19T18:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: Transactions within transactions</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39340#M8971</link>
      <description>&lt;P&gt;AFAICT from the logs, and because I am doing a transaction based upon the RID, the connect is just the next sequential step after the DAO START.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2013 18:45:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39340#M8971</guid>
      <dc:creator>tyronetv</dc:creator>
      <dc:date>2013-08-19T18:45:57Z</dc:date>
    </item>
    <item>
      <title>Re: Transactions within transactions</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39341#M8972</link>
      <description>&lt;P&gt;Perhaps something like&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | transaction RID startswith="DAO CALL START" endswith="java.sql.Connection" | search duration&amp;gt;1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;?&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2013 19:00:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39341#M8972</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-08-19T19:00:45Z</dc:date>
    </item>
    <item>
      <title>Re: Transactions within transactions</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39342#M8973</link>
      <description>&lt;P&gt;Doesn't work.  Been there done that. &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;As you can see from my example, there are multiple connections to the DB under one RID.  &lt;/P&gt;

&lt;P&gt;I need each one encapsulated and that search didn't do it for me.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2013 20:00:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39342#M8973</guid>
      <dc:creator>tyronetv</dc:creator>
      <dc:date>2013-08-19T20:00:10Z</dc:date>
    </item>
    <item>
      <title>Re: Transactions within transactions</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39343#M8974</link>
      <description>&lt;P&gt;The &lt;CODE&gt;startswith&lt;/CODE&gt; argument means &lt;CODE&gt;transaction&lt;/CODE&gt; will begin a new transaction whenever it sees that string. What are your results when you use this?&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2013 20:11:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39343#M8974</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-08-19T20:11:47Z</dc:date>
    </item>
    <item>
      <title>Re: Transactions within transactions</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39344#M8975</link>
      <description>&lt;P&gt;transaction RID startswith="DAO CALL START" endswith=" Connection" &lt;/P&gt;

&lt;P&gt;Yeah... I should of figured that out sooner.&lt;/P&gt;

&lt;P&gt;Thanks for the assist though.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2013 10:14:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-within-transactions/m-p/39344#M8975</guid>
      <dc:creator>tyronetv</dc:creator>
      <dc:date>2013-08-21T10:14:59Z</dc:date>
    </item>
  </channel>
</rss>

