<?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 Transactions events at the same second in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Transactions-events-at-the-same-second/m-p/406265#M117434</link>
    <description>&lt;P&gt;I am using the transaction command to identify if a report runs over a certain time. Below is my search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| transaction startswith="Start" endswith="Finish" keeporphans=true
| where _txn_orphan=1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This primarily is working except there seem to be some false positives. If a report runs and finishes within the same second (which happens if a user forgets a parameter) Splunk is still counting it as orphaned, so _txn_orphan is still 1 but it should be 0 since it actually completed. Has anyone run into this and have a better way or workaround for this? &lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2020 00:48:32 GMT</pubDate>
    <dc:creator>aohls</dc:creator>
    <dc:date>2020-09-30T00:48:32Z</dc:date>
    <item>
      <title>Transactions events at the same second</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-events-at-the-same-second/m-p/406265#M117434</link>
      <description>&lt;P&gt;I am using the transaction command to identify if a report runs over a certain time. Below is my search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| transaction startswith="Start" endswith="Finish" keeporphans=true
| where _txn_orphan=1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This primarily is working except there seem to be some false positives. If a report runs and finishes within the same second (which happens if a user forgets a parameter) Splunk is still counting it as orphaned, so _txn_orphan is still 1 but it should be 0 since it actually completed. Has anyone run into this and have a better way or workaround for this? &lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:48:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-events-at-the-same-second/m-p/406265#M117434</guid>
      <dc:creator>aohls</dc:creator>
      <dc:date>2020-09-30T00:48:32Z</dc:date>
    </item>
    <item>
      <title>Re: Transactions events at the same second</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-events-at-the-same-second/m-p/406266#M117435</link>
      <description>&lt;P&gt;Hi @aohls,&lt;/P&gt;

&lt;P&gt;You can easily get rid of this by adding to your condition a minimum duration for the transaction. That way all those noisy transaction won't show anymore &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Cheers,&lt;BR /&gt;
David&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2019 12:53:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-events-at-the-same-second/m-p/406266#M117435</guid>
      <dc:creator>DavidHourani</dc:creator>
      <dc:date>2019-06-06T12:53:26Z</dc:date>
    </item>
  </channel>
</rss>

