<?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 How can we handle complex alert scheduling? in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/How-can-we-handle-complex-alert-scheduling/m-p/519735#M9679</link>
    <description>&lt;P&gt;How do we handle an alert that needs to run on certain hours on Saturday and on different hours on Sunday. Can the cron expression express something like that?&lt;/P&gt;&lt;P&gt;We ended up placing the scheduling logic in the query itself.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Sep 2020 15:07:01 GMT</pubDate>
    <dc:creator>danielbb</dc:creator>
    <dc:date>2020-09-15T15:07:01Z</dc:date>
    <item>
      <title>How can we handle complex alert scheduling?</title>
      <link>https://community.splunk.com/t5/Alerting/How-can-we-handle-complex-alert-scheduling/m-p/519735#M9679</link>
      <description>&lt;P&gt;How do we handle an alert that needs to run on certain hours on Saturday and on different hours on Sunday. Can the cron expression express something like that?&lt;/P&gt;&lt;P&gt;We ended up placing the scheduling logic in the query itself.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2020 15:07:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/How-can-we-handle-complex-alert-scheduling/m-p/519735#M9679</guid>
      <dc:creator>danielbb</dc:creator>
      <dc:date>2020-09-15T15:07:01Z</dc:date>
    </item>
    <item>
      <title>Re: How can we handle complex alert scheduling?</title>
      <link>https://community.splunk.com/t5/Alerting/How-can-we-handle-complex-alert-scheduling/m-p/519741#M9680</link>
      <description>&lt;P&gt;You would need two alerts, one with a cron expression for Saturday hours and another for Sunday hours.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2020 15:30:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/How-can-we-handle-complex-alert-scheduling/m-p/519741#M9680</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2020-09-15T15:30:48Z</dc:date>
    </item>
    <item>
      <title>Re: How can we handle complex alert scheduling?</title>
      <link>https://community.splunk.com/t5/Alerting/How-can-we-handle-complex-alert-scheduling/m-p/519752#M9682</link>
      <description>&lt;P&gt;As&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/225168"&gt;@ITWhisperer&lt;/a&gt;&amp;nbsp;already said, the common way to do it is add as many “alerts” as needed with own schedules. Query should be the same, but probably it’s easier to add earliest+ latest to it than trust those which are on alert definition.&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2020 16:33:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/How-can-we-handle-complex-alert-scheduling/m-p/519752#M9682</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2020-09-15T16:33:45Z</dc:date>
    </item>
  </channel>
</rss>

