<?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 scheduling works? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238846#M188733</link>
    <description>&lt;P&gt;Glad to help! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 17 Aug 2016 16:20:24 GMT</pubDate>
    <dc:creator>horsefez</dc:creator>
    <dc:date>2016-08-17T16:20:24Z</dc:date>
    <item>
      <title>How scheduling works?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238841#M188728</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have a scheduled search that runs every 1 minute and it searches events on last 1 minute.&lt;/P&gt;

&lt;P&gt;Will this search cover all future events?&lt;BR /&gt;
If the search could start (for example) at 5:07:05 and than at 5:08:07 - are the data from (5:07:05 - 5:07:07) lost?&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2016 12:42:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238841#M188728</guid>
      <dc:creator>lukasz92</dc:creator>
      <dc:date>2016-08-17T12:42:29Z</dc:date>
    </item>
    <item>
      <title>Re: How scheduling works?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238842#M188729</link>
      <description>&lt;P&gt;What are you trying to accomplish with your scheduled search? Do you have an alert tied to this scheduled search?&lt;/P&gt;

&lt;P&gt;You set the time window for 1 minute, so technically the data is not "lost", but the data is not available in your 1 minute window if it's older than 1 minute&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2016 12:51:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238842#M188729</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2016-08-17T12:51:47Z</dc:date>
    </item>
    <item>
      <title>Re: How scheduling works?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238843#M188730</link>
      <description>&lt;P&gt;Hi lukasz92, &lt;/P&gt;

&lt;P&gt;there is a solution to your problem.&lt;/P&gt;

&lt;P&gt;Try to apply the following settings to your alert&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/1743i2AEE97D9EF7E2D43/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;This will asure, that everything from 02:46:00 to 02:47:00 is covered. The alert is able to run between 02:47:00 and 02:47:59 and will still catch the data.&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;&lt;STRONG&gt;BUT&lt;/STRONG&gt;, splunk takes time to index data... so data that reaches the machine on 02:46:59 might not be indexed by 02:47:00... so you should try to make like a little "window" for your alert to run in... do that in the Cron-Expression field.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2016 12:53:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238843#M188730</guid>
      <dc:creator>horsefez</dc:creator>
      <dc:date>2016-08-17T12:53:11Z</dc:date>
    </item>
    <item>
      <title>Re: How scheduling works?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238844#M188731</link>
      <description>&lt;P&gt;Yes, Something like searching for custom events and alerting. &lt;/P&gt;

&lt;P&gt;Technically I agree and understand - my question was about practice: how this does actually work.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2016 13:28:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238844#M188731</guid>
      <dc:creator>lukasz92</dc:creator>
      <dc:date>2016-08-17T13:28:07Z</dc:date>
    </item>
    <item>
      <title>Re: How scheduling works?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238845#M188732</link>
      <description>&lt;P&gt;it is a great solution. I have not thought about "@m".&lt;BR /&gt;
Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2016 13:30:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238845#M188732</guid>
      <dc:creator>lukasz92</dc:creator>
      <dc:date>2016-08-17T13:30:23Z</dc:date>
    </item>
    <item>
      <title>Re: How scheduling works?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238846#M188733</link>
      <description>&lt;P&gt;Glad to help! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2016 16:20:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-scheduling-works/m-p/238846#M188733</guid>
      <dc:creator>horsefez</dc:creator>
      <dc:date>2016-08-17T16:20:24Z</dc:date>
    </item>
  </channel>
</rss>

