<?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 Per Second in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Transactions-Per-Second/m-p/27708#M148011</link>
    <description>&lt;P&gt;Here are some options: &lt;/P&gt;

&lt;P&gt;1) &lt;CODE&gt;&amp;lt;your transaction search&amp;gt; | timechart count span=1s&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;However if this returns more than 50,000 results it wont work and it'll return that bucketing error. &lt;/P&gt;

&lt;P&gt;2) another idea is to use per_second.  Confusingly, per_second needs a numeric quantity. The good news is that you can just make one with eval. =)
Try this: &lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;&amp;lt;your transaction search&amp;gt; | eval count=1 | timechart per_second(count) as transactions_per_second&lt;/CODE&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Aug 2010 06:01:12 GMT</pubDate>
    <dc:creator>sideview</dc:creator>
    <dc:date>2010-08-11T06:01:12Z</dc:date>
    <item>
      <title>Transactions Per Second</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-Per-Second/m-p/27707#M148010</link>
      <description>&lt;P&gt;What is the best way to determine transactions per second are occurring in our application logs.  I attempted using " ... | bucket _time span=1s | stats count by _time" but I received a bucket span error because this search would result in &amp;gt; 50,000 bins.  I also attempted to use the timechart per_second function does not provided the data I am looking for.  Would stats be the best command to use.  There is also the localize command, but I am not sure what the count and density fields actually represent?&lt;/P&gt;</description>
      <pubDate>Wed, 11 Aug 2010 04:41:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-Per-Second/m-p/27707#M148010</guid>
      <dc:creator>kbecker</dc:creator>
      <dc:date>2010-08-11T04:41:35Z</dc:date>
    </item>
    <item>
      <title>Re: Transactions Per Second</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-Per-Second/m-p/27708#M148011</link>
      <description>&lt;P&gt;Here are some options: &lt;/P&gt;

&lt;P&gt;1) &lt;CODE&gt;&amp;lt;your transaction search&amp;gt; | timechart count span=1s&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;However if this returns more than 50,000 results it wont work and it'll return that bucketing error. &lt;/P&gt;

&lt;P&gt;2) another idea is to use per_second.  Confusingly, per_second needs a numeric quantity. The good news is that you can just make one with eval. =)
Try this: &lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;&amp;lt;your transaction search&amp;gt; | eval count=1 | timechart per_second(count) as transactions_per_second&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Aug 2010 06:01:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-Per-Second/m-p/27708#M148011</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2010-08-11T06:01:12Z</dc:date>
    </item>
    <item>
      <title>Re: Transactions Per Second</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transactions-Per-Second/m-p/27709#M148012</link>
      <description>&lt;P&gt;I use the timechart command, but in the Summary Index context. Run this search once per hour (or whatever timeframe reduces the results enough to make it work).&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;your transaction search&amp;gt;  | sitimechart span=1s count
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Access the results with:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=summary search_name="Summary Logins Per Second" | timechart span=1s count
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Unfortunately, that means 86400 results per 24 hour period, so reporting over longer ranges will still require some tinkering.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Aug 2010 02:53:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transactions-Per-Second/m-p/27709#M148012</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2010-08-12T02:53:35Z</dc:date>
    </item>
  </channel>
</rss>

