<?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 transaction command in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/transaction-command/m-p/482376#M135135</link>
    <description>&lt;P&gt;I have many events against session_id. but I am interested to only list down three type of events &lt;/P&gt;

&lt;P&gt;1- AD authentication successful&lt;BR /&gt;
2- RADUS authentication successful&lt;BR /&gt;
3- SMS generated&lt;/P&gt;

&lt;P&gt;Please advise&lt;/P&gt;</description>
    <pubDate>Mon, 13 Jan 2020 08:04:03 GMT</pubDate>
    <dc:creator>riqbal47010</dc:creator>
    <dc:date>2020-01-13T08:04:03Z</dc:date>
    <item>
      <title>transaction command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/transaction-command/m-p/482376#M135135</link>
      <description>&lt;P&gt;I have many events against session_id. but I am interested to only list down three type of events &lt;/P&gt;

&lt;P&gt;1- AD authentication successful&lt;BR /&gt;
2- RADUS authentication successful&lt;BR /&gt;
3- SMS generated&lt;/P&gt;

&lt;P&gt;Please advise&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jan 2020 08:04:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/transaction-command/m-p/482376#M135135</guid>
      <dc:creator>riqbal47010</dc:creator>
      <dc:date>2020-01-13T08:04:03Z</dc:date>
    </item>
    <item>
      <title>Re: transaction command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/transaction-command/m-p/482377#M135136</link>
      <description>&lt;P&gt;There could be many ways to optimize your query, if you provided one. However, with the information you provided, I might start with the text of those events and put that text in my base query. Let's say your "AD authentication successful" has that actual text in the events. Then in your base query (meaning the query before the first pipe):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=yourindex source=yoursource sourcetype=yoursourcetype "*AD authentication successful*" rest of your base query
| your other statements
| transaction command details
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then when you run the query, your base query has already filtered down to the information you are looking for. As making your base query as specific as possible is also a best practice, you will gain the additional benefit of having a faster query.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jan 2020 13:59:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/transaction-command/m-p/482377#M135136</guid>
      <dc:creator>efavreau</dc:creator>
      <dc:date>2020-01-13T13:59:10Z</dc:date>
    </item>
    <item>
      <title>Re: transaction command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/transaction-command/m-p/482378#M135137</link>
      <description>&lt;P&gt;Also need to make sure that if "| your other statements" changes the order of the events, you'll need to use the sort command to put them back in reverse time order.  The transaction command requires that.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jan 2020 15:46:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/transaction-command/m-p/482378#M135137</guid>
      <dc:creator>rmmiller</dc:creator>
      <dc:date>2020-01-13T15:46:45Z</dc:date>
    </item>
  </channel>
</rss>

