<?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: Subsearch hitting limit. How to circumvent in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Subsearch-hitting-limit-How-to-circumvent/m-p/141711#M2290</link>
    <description>&lt;P&gt;It would, but the smaller search is faster it takes more than 60 seconds to complete.&lt;/P&gt;</description>
    <pubDate>Mon, 14 Jul 2014 22:03:56 GMT</pubDate>
    <dc:creator>steven10172</dc:creator>
    <dc:date>2014-07-14T22:03:56Z</dc:date>
    <item>
      <title>Subsearch hitting limit. How to circumvent</title>
      <link>https://community.splunk.com/t5/Alerting/Subsearch-hitting-limit-How-to-circumvent/m-p/141708#M2287</link>
      <description>&lt;P&gt;I'm currently working on developing a search that will be run every 15minutes as an Alert. I would like the alert to only send an email if the usage has increased more than a certain threshold of the average usage.&lt;/P&gt;

&lt;P&gt;In the query below I grab the usage for the last 15minutes and compare it to the average usage for the previous 24hrs. I only show results where the current usage is at least 2x the average usage so I can trigger an alert based on the number of results returned.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;* index=voice earliest=-15m latest=-0m
| fields _raw,host
| eval bytes=len(_raw)
| eval kilobytes=bytes/1024
| eval uncompressedKB=kilobytes/.6
| stats sum(uncompressedKB) as Last15Minutes by host
| join host [ search * index=voice earliest=-25h@h latest=-1h@h
    | fields _raw,host
    | eval tmp_bytes=len(_raw)
    | eval tmp_kilobytes=tmp_bytes/1024
    | eval tmp_uncompressedKB=tmp_kilobytes/.6
    | stats sum(tmp_uncompressedKB) as Last24Hour by host ]
| eval avgKB=Last24Hour/24/60*15 
| where (avgKB*2.00)&amp;lt;a
| table host,Last15Minutes,Last24Hour,avgKB
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The issue I'm having is that the average is really low and it seems that I'm hitting a 60second search limit. Is there a way to combine the subsearch into the main search or make the subsearch be it's own automated search that gets cached?&lt;/P&gt;

&lt;P&gt;P.S. I don't have access to the .conf's&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2014 21:27:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Subsearch-hitting-limit-How-to-circumvent/m-p/141708#M2287</guid>
      <dc:creator>steven10172</dc:creator>
      <dc:date>2014-07-14T21:27:18Z</dc:date>
    </item>
    <item>
      <title>Re: Subsearch hitting limit. How to circumvent</title>
      <link>https://community.splunk.com/t5/Alerting/Subsearch-hitting-limit-How-to-circumvent/m-p/141709#M2288</link>
      <description>&lt;P&gt;If you pull out the sub search and schedule it, you can refer to the most recent results via the &lt;CODE&gt;| loadjob&lt;/CODE&gt; command.  (&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.2/SearchReference/Loadjob"&gt;Splunk Reference&lt;/A&gt;)&lt;/P&gt;

&lt;P&gt;Another idea is to use summary indexing to store the aggregate data in various time slices, and then search that for your final output, but that's more complicated.  &lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2014 21:48:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Subsearch-hitting-limit-How-to-circumvent/m-p/141709#M2288</guid>
      <dc:creator>emiller42</dc:creator>
      <dc:date>2014-07-14T21:48:39Z</dc:date>
    </item>
    <item>
      <title>Re: Subsearch hitting limit. How to circumvent</title>
      <link>https://community.splunk.com/t5/Alerting/Subsearch-hitting-limit-How-to-circumvent/m-p/141710#M2289</link>
      <description>&lt;P&gt;Wouldn't the easiest way around the default subsearch time limit be to reverse your searches, i.e. make the narrower search your subsearch?&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2014 21:50:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Subsearch-hitting-limit-How-to-circumvent/m-p/141710#M2289</guid>
      <dc:creator>chanfoli</dc:creator>
      <dc:date>2014-07-14T21:50:50Z</dc:date>
    </item>
    <item>
      <title>Re: Subsearch hitting limit. How to circumvent</title>
      <link>https://community.splunk.com/t5/Alerting/Subsearch-hitting-limit-How-to-circumvent/m-p/141711#M2290</link>
      <description>&lt;P&gt;It would, but the smaller search is faster it takes more than 60 seconds to complete.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2014 22:03:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Subsearch-hitting-limit-How-to-circumvent/m-p/141711#M2290</guid>
      <dc:creator>steven10172</dc:creator>
      <dc:date>2014-07-14T22:03:56Z</dc:date>
    </item>
  </channel>
</rss>

