<?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: What are some alerts scheduling methods and best practices? in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/What-are-some-alerts-scheduling-methods-and-best-practices/m-p/451267#M7976</link>
    <description>&lt;P&gt;Assuming you've not changed the related settings, 16 CPUs can run 22 searches simultaneously.  Half of that is for scheduled searches so you can run 11 alerts at a time.&lt;/P&gt;

&lt;P&gt;Have you looked in the Monitoring Console for skipped searches?  You probably have a lot of them.&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jun 2019 20:20:18 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2019-06-27T20:20:18Z</dc:date>
    <item>
      <title>What are some alerts scheduling methods and best practices?</title>
      <link>https://community.splunk.com/t5/Alerting/What-are-some-alerts-scheduling-methods-and-best-practices/m-p/451264#M7973</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;

&lt;P&gt;We are trying to reduce the concurrent search count in our environment as upgrading hardware resource is not possible. We have a dedicated alerting which is running about 800 alerts at different frequency. FOR EXAMPLE :&lt;/P&gt;

&lt;P&gt;There are around 400 alerts which is running at every 15 min interval defined as such - (*/15 * * * *) in cron meaning the alerts are running at 10 AM,10:15 AM,10:30 etc. &lt;/P&gt;

&lt;P&gt;We are planning to schedule the cron job as such  -&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;100  alerts at 10 AM,10:15 AM,10:30 etc. (*/15 * * * *)
100 alerts at 10:1 AM ,10:16 AM,10.31 AM and so on (1/15 * * * *  )
100 alerts at 10:2 AM ,10:17 AM,10.32 AM and so on (2/15 * * * *  )
100 alerts at 10:3 AM ,10:18 AM,10.33 AM and so on (3/15 * * * *  )
100 alerts at 10:4 AM ,10:19 AM,10.34 AM and so on (4/15 * * * *  )
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Please suggest if this is a good way of scheduling alerts and do suggest if there are other methods.&lt;/P&gt;

&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2019 16:35:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/What-are-some-alerts-scheduling-methods-and-best-practices/m-p/451264#M7973</guid>
      <dc:creator>keishamtcs</dc:creator>
      <dc:date>2019-06-27T16:35:38Z</dc:date>
    </item>
    <item>
      <title>Re: What are some alerts scheduling methods and best practices?</title>
      <link>https://community.splunk.com/t5/Alerting/What-are-some-alerts-scheduling-methods-and-best-practices/m-p/451265#M7974</link>
      <description>&lt;P&gt;Spreading schedule searches and alerts across time is a good idea.  Here are some other considerations:&lt;/P&gt;

&lt;P&gt;When scheduling alerts, consider how long each alert takes to run.  It's not helpful to schedule 100 searches each minute if they take longer than a minute to complete.&lt;/P&gt;

&lt;P&gt;Don't schedule more alerts at a time than you have CPUs available.&lt;/P&gt;

&lt;P&gt;I always recommend setting &lt;CODE&gt;schedule_window = auto&lt;/CODE&gt; for all scheduled searches.&lt;/P&gt;

&lt;P&gt;Review the alerts to determine if they all really need to run every 15 minutes or if some can run less often.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2019 18:07:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/What-are-some-alerts-scheduling-methods-and-best-practices/m-p/451265#M7974</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-06-27T18:07:31Z</dc:date>
    </item>
    <item>
      <title>Re: What are some alerts scheduling methods and best practices?</title>
      <link>https://community.splunk.com/t5/Alerting/What-are-some-alerts-scheduling-methods-and-best-practices/m-p/451266#M7975</link>
      <description>&lt;P&gt;Hi Rich,&lt;/P&gt;

&lt;P&gt;Thanks for the update. we have 16 core CPU so how many alerts can we configure ?&lt;BR /&gt;
Yes its only after removing the unwanted alerts, it came down to 400 or something.&lt;BR /&gt;
So we are trying to come up with a effective solution for this.&lt;/P&gt;

&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2019 18:16:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/What-are-some-alerts-scheduling-methods-and-best-practices/m-p/451266#M7975</guid>
      <dc:creator>keishamtcs</dc:creator>
      <dc:date>2019-06-27T18:16:05Z</dc:date>
    </item>
    <item>
      <title>Re: What are some alerts scheduling methods and best practices?</title>
      <link>https://community.splunk.com/t5/Alerting/What-are-some-alerts-scheduling-methods-and-best-practices/m-p/451267#M7976</link>
      <description>&lt;P&gt;Assuming you've not changed the related settings, 16 CPUs can run 22 searches simultaneously.  Half of that is for scheduled searches so you can run 11 alerts at a time.&lt;/P&gt;

&lt;P&gt;Have you looked in the Monitoring Console for skipped searches?  You probably have a lot of them.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2019 20:20:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/What-are-some-alerts-scheduling-methods-and-best-practices/m-p/451267#M7976</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-06-27T20:20:18Z</dc:date>
    </item>
  </channel>
</rss>

