<?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: Scheduling multiple searches in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216271#M63413</link>
    <description>&lt;P&gt;Thanks for the help! You answered another one of my questions on tstats as well which was very helpful. As mentioned in the above post, I am creating a kinda search inception and am wondering how my 2nd,3rd,4th search string would be written? &lt;/P&gt;

&lt;P&gt;EG - (Event count) - The initial 10min search to populate the SI is - | tstats count WHERE index=test* earliest=-10m@m latest=@m by _time span=10m &lt;/P&gt;

&lt;P&gt;How would I shape that search for the other 3 SI's populating searches, based on the first SI, so that I can ultimately use anyone of the 4 I choose as a single value with trendline on my dashboard? &lt;/P&gt;</description>
    <pubDate>Tue, 09 Aug 2016 15:02:26 GMT</pubDate>
    <dc:creator>mansel_scheffel</dc:creator>
    <dc:date>2016-08-09T15:02:26Z</dc:date>
    <item>
      <title>Scheduling multiple searches</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216269#M63411</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am trying to schedule 60 saved searches with summery indexing. There are for 5 different searches, each with 4 schedules - 10min, 1h, 1d, 1w. The initial 10min search will summarise, from there I want the 1h search to create an SI from the 10min SI, the 1d to create an SI from the 1h SI, etc. &lt;/P&gt;

&lt;P&gt;-What would be the best way to do this in terms of setting schedule windows&lt;BR /&gt;
-How can I catch up for delayed data, populate the latest period and verify the previous one if possible?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 09 Aug 2016 10:05:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216269#M63411</guid>
      <dc:creator>mansel_scheffel</dc:creator>
      <dc:date>2016-08-09T10:05:38Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduling multiple searches</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216270#M63412</link>
      <description>&lt;P&gt;To take care of indexing latency, your time range should go little earlier then the current time.&lt;/P&gt;

&lt;P&gt;E.g. For 10 min searches, the time range can be &lt;CODE&gt;-15m@m to 5m@m&lt;/CODE&gt;, allowing 5 min extra for new events to become searchable. The cron can be this &lt;CODE&gt;3-59/10 * * * *&lt;/CODE&gt; (running on 3,13,23.. min of every hour).&lt;BR /&gt;
For this same 10 min search, the data for last hour will get completed after 3rd min execution of 10 min search, so the time range for 1 hour this can will be &lt;CODE&gt;-1h@h to @h&lt;/CODE&gt; with cron as &lt;CODE&gt;15 * * * *&lt;/CODE&gt; &lt;BR /&gt;
The daily search's time range will be &lt;CODE&gt;-1d@d to @d&lt;/CODE&gt;, with cron &lt;CODE&gt;11 1 * * *&lt;/CODE&gt; (allowing adding 1 hour 11 min for hourly data to be completed)&lt;BR /&gt;
The weekly search's time range will be &lt;CODE&gt;-1w@w to @w&lt;/CODE&gt;, with cron &lt;CODE&gt;22 2 * * 1&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Aug 2016 14:55:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216270#M63412</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2016-08-09T14:55:33Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduling multiple searches</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216271#M63413</link>
      <description>&lt;P&gt;Thanks for the help! You answered another one of my questions on tstats as well which was very helpful. As mentioned in the above post, I am creating a kinda search inception and am wondering how my 2nd,3rd,4th search string would be written? &lt;/P&gt;

&lt;P&gt;EG - (Event count) - The initial 10min search to populate the SI is - | tstats count WHERE index=test* earliest=-10m@m latest=@m by _time span=10m &lt;/P&gt;

&lt;P&gt;How would I shape that search for the other 3 SI's populating searches, based on the first SI, so that I can ultimately use anyone of the 4 I choose as a single value with trendline on my dashboard? &lt;/P&gt;</description>
      <pubDate>Tue, 09 Aug 2016 15:02:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216271#M63413</guid>
      <dc:creator>mansel_scheffel</dc:creator>
      <dc:date>2016-08-09T15:02:26Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduling multiple searches</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216272#M63414</link>
      <description>&lt;P&gt;After you set your 10 min search using above tstats query, your 10 min SI will have (listing main fields only) fields _time and count, with field count not being an indexed fields (fields gets ingested as kv pair in SI). &lt;/P&gt;

&lt;P&gt;So your other SI searches would use regular stats/timechart command, like this&lt;/P&gt;

&lt;P&gt;Hourly&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=your10MinSI source="your10MinSISearchName" earliest=-1h@h latest=@h | timechart span=1h sum(count) as count
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Daily&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=your1HourSI source="your1HourSISearchName" earliest=-1d@d latest=@d | timechart span=1d sum(count) as count
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Weekly&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=your1DaySI source="your1DaySISearchName" earliest=-1w@w latest=@w | timechart span=1w sum(count) as count
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 09 Aug 2016 15:20:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216272#M63414</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2016-08-09T15:20:42Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduling multiple searches</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216273#M63415</link>
      <description>&lt;P&gt;Awesome thanks a lot !!&lt;/P&gt;</description>
      <pubDate>Tue, 09 Aug 2016 15:24:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216273#M63415</guid>
      <dc:creator>mansel_scheffel</dc:creator>
      <dc:date>2016-08-09T15:24:52Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduling multiple searches</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216274#M63416</link>
      <description>&lt;P&gt;With regards to the above - if I dont want to have buckets that are say 09.48 -0 9.58 can I change the cron jobs to run at 5-59/10 * * * * and so on, so that my time will be on 09.50 - 10.00 etc? &lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2016 09:33:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Scheduling-multiple-searches/m-p/216274#M63416</guid>
      <dc:creator>mansel_scheffel</dc:creator>
      <dc:date>2016-08-11T09:33:43Z</dc:date>
    </item>
  </channel>
</rss>

