<?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: How does a Schedule Saved Search work? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-does-a-Schedule-Saved-Search-work/m-p/12972#M1104</link>
    <description>&lt;P&gt;No, scheduled searches are not that smart.  It will run over 'All Time' every time it runs, that is the time-range that you have originally configured.&lt;/P&gt;

&lt;P&gt;I realise that this is only an example, but in general, 'all time' searches are very resource intensive and scheduled searches should be optimized as much as possible.  If you want to run a search every 24 hours, then you only need to search the last 24 hours - starthoursago=24 -  similarly, if you're running an hourly search, you'll want to specify something like starthoursago=1&lt;/P&gt;</description>
    <pubDate>Thu, 06 May 2010 09:51:59 GMT</pubDate>
    <dc:creator>mctester</dc:creator>
    <dc:date>2010-05-06T09:51:59Z</dc:date>
    <item>
      <title>How does a Schedule Saved Search work?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-does-a-Schedule-Saved-Search-work/m-p/12971#M1103</link>
      <description>&lt;P&gt;Hi  &lt;/P&gt;

&lt;P&gt;I have a question about the workings of the scheduled saved search. Suppose I have a slow-running search that has been scheduled to run every day. The time-range for this search is All-Time. Does the search run over the "all-time" period for every consecutive run after a successful previous run? Or is it smart enough to run only for the delta of the elapsed time between the last successful run and the present time?  &lt;/P&gt;

&lt;P&gt;Thanks for your input.  &lt;/P&gt;

&lt;P&gt;Ranga&lt;/P&gt;</description>
      <pubDate>Thu, 06 May 2010 05:23:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-does-a-Schedule-Saved-Search-work/m-p/12971#M1103</guid>
      <dc:creator>sranga</dc:creator>
      <dc:date>2010-05-06T05:23:29Z</dc:date>
    </item>
    <item>
      <title>Re: How does a Schedule Saved Search work?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-does-a-Schedule-Saved-Search-work/m-p/12972#M1104</link>
      <description>&lt;P&gt;No, scheduled searches are not that smart.  It will run over 'All Time' every time it runs, that is the time-range that you have originally configured.&lt;/P&gt;

&lt;P&gt;I realise that this is only an example, but in general, 'all time' searches are very resource intensive and scheduled searches should be optimized as much as possible.  If you want to run a search every 24 hours, then you only need to search the last 24 hours - starthoursago=24 -  similarly, if you're running an hourly search, you'll want to specify something like starthoursago=1&lt;/P&gt;</description>
      <pubDate>Thu, 06 May 2010 09:51:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-does-a-Schedule-Saved-Search-work/m-p/12972#M1104</guid>
      <dc:creator>mctester</dc:creator>
      <dc:date>2010-05-06T09:51:59Z</dc:date>
    </item>
  </channel>
</rss>

