<?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: Cron job condition when running DBX query in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Cron-job-condition-when-running-DBX-query/m-p/335311#M5008</link>
    <description>&lt;P&gt;Run the Monday one with a regular cron then every year go through and figure out when the holiday things are and setup INDIVIDUAL jobs for each Tuesday, writing the queries in such a way that the Tuesday run always overwrites the previous day's run.&lt;/P&gt;</description>
    <pubDate>Sat, 03 Jun 2017 17:28:37 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2017-06-03T17:28:37Z</dc:date>
    <item>
      <title>Cron job condition when running DBX query</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Cron-job-condition-when-running-DBX-query/m-p/335310#M5007</link>
      <description>&lt;P&gt;Hi, &lt;BR /&gt;
I have a condition where we have to run dbxquery command based on scheduling condition..  Only on Mondays between 8 am to 2 pm..  Incase if Monday is public holiday it should run on Tuesday..  How can we achieve this? &lt;/P&gt;</description>
      <pubDate>Sat, 03 Jun 2017 16:56:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Cron-job-condition-when-running-DBX-query/m-p/335310#M5007</guid>
      <dc:creator>k_harini</dc:creator>
      <dc:date>2017-06-03T16:56:58Z</dc:date>
    </item>
    <item>
      <title>Re: Cron job condition when running DBX query</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Cron-job-condition-when-running-DBX-query/m-p/335311#M5008</link>
      <description>&lt;P&gt;Run the Monday one with a regular cron then every year go through and figure out when the holiday things are and setup INDIVIDUAL jobs for each Tuesday, writing the queries in such a way that the Tuesday run always overwrites the previous day's run.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jun 2017 17:28:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Cron-job-condition-when-running-DBX-query/m-p/335311#M5008</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-06-03T17:28:37Z</dc:date>
    </item>
    <item>
      <title>Re: Cron job condition when running DBX query</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Cron-job-condition-when-running-DBX-query/m-p/335312#M5009</link>
      <description>&lt;P&gt;How to make Tuesday run overwrite?  Here we have used saved search with dbxquery and summary indexed the data.. I can have a look up list  of public holidays.  With tat how can I change cron job? &lt;/P&gt;</description>
      <pubDate>Sun, 04 Jun 2017 01:49:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Cron-job-condition-when-running-DBX-query/m-p/335312#M5009</guid>
      <dc:creator>k_harini</dc:creator>
      <dc:date>2017-06-04T01:49:30Z</dc:date>
    </item>
    <item>
      <title>Re: Cron job condition when running DBX query</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Cron-job-condition-when-running-DBX-query/m-p/335313#M5010</link>
      <description>&lt;P&gt;Keep the same search that should end in &lt;CODE&gt;| collect&lt;/CODE&gt;and add to it something like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| search ThisFieldDoesNotExist="So this will throw away all the events we just saved"
| append [ search [|makeresults | eval search = "earliest=-1d@d latest=0d@d-1" | table search] index="YourSummaryIndexHere"
|delete ]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sun, 04 Jun 2017 03:54:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Cron-job-condition-when-running-DBX-query/m-p/335313#M5010</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-06-04T03:54:06Z</dc:date>
    </item>
  </channel>
</rss>

