<?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 Alert skipped - out of search disk space in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Alert-skipped-out-of-search-disk-space/m-p/279266#M12554</link>
    <description>&lt;P&gt;We are currently running Splunk 6.2.3.  One user has created an alert which for some reason is being skipped with the reason "Out of search disk space".&lt;/P&gt;

&lt;P&gt;04-07-2016 23:55:01.126 -0400 INFO  SavedSplunker - savedsearch_id="nobody;custom_app;Watch Team - After Hours", user="user1", app="custom_app", savedsearch_name="Watch Team - After Hours", status=skipped, reason="Out of search disk space.", scheduled_time=1460087700&lt;/P&gt;

&lt;P&gt;04-07-2016 23:55:01.126 -0400 WARN  SavedSplunker - Max alive instance_count=1 reached for savedsearch_id="nobody;custom_app;Watch Team - After Hours"&lt;/P&gt;

&lt;P&gt;A user who is a member of the admin role cloned and scheduled the search, and it ran without issue.&lt;/P&gt;

&lt;P&gt;After investigating the issue I found "rtSrchJobsQuota = 6" in the /etc/system/default/authorize.conf file.  The user in question had previously configured/scheduled 6 searches/alerts - this would be the 7th.  Am I correct in deducing that the rtSrchjobsQuota value is what is preventing this alert from running?  If yes, would scheduled searches/alerts be considered "real time"?&lt;/P&gt;

&lt;P&gt;Thank you.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 09:20:01 GMT</pubDate>
    <dc:creator>adamblock2</dc:creator>
    <dc:date>2020-09-29T09:20:01Z</dc:date>
    <item>
      <title>Alert skipped - out of search disk space</title>
      <link>https://community.splunk.com/t5/Alerting/Alert-skipped-out-of-search-disk-space/m-p/279266#M12554</link>
      <description>&lt;P&gt;We are currently running Splunk 6.2.3.  One user has created an alert which for some reason is being skipped with the reason "Out of search disk space".&lt;/P&gt;

&lt;P&gt;04-07-2016 23:55:01.126 -0400 INFO  SavedSplunker - savedsearch_id="nobody;custom_app;Watch Team - After Hours", user="user1", app="custom_app", savedsearch_name="Watch Team - After Hours", status=skipped, reason="Out of search disk space.", scheduled_time=1460087700&lt;/P&gt;

&lt;P&gt;04-07-2016 23:55:01.126 -0400 WARN  SavedSplunker - Max alive instance_count=1 reached for savedsearch_id="nobody;custom_app;Watch Team - After Hours"&lt;/P&gt;

&lt;P&gt;A user who is a member of the admin role cloned and scheduled the search, and it ran without issue.&lt;/P&gt;

&lt;P&gt;After investigating the issue I found "rtSrchJobsQuota = 6" in the /etc/system/default/authorize.conf file.  The user in question had previously configured/scheduled 6 searches/alerts - this would be the 7th.  Am I correct in deducing that the rtSrchjobsQuota value is what is preventing this alert from running?  If yes, would scheduled searches/alerts be considered "real time"?&lt;/P&gt;

&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 09:20:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alert-skipped-out-of-search-disk-space/m-p/279266#M12554</guid>
      <dc:creator>adamblock2</dc:creator>
      <dc:date>2020-09-29T09:20:01Z</dc:date>
    </item>
    <item>
      <title>Re: Alert skipped - out of search disk space</title>
      <link>https://community.splunk.com/t5/Alerting/Alert-skipped-out-of-search-disk-space/m-p/279267#M12555</link>
      <description>&lt;P&gt;Hi adamblock2, based on the error it seems likely that the user is running into a srchDiskQuota limitation. Check the spec on authorize.conf for more info &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/authorizeconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/authorizeconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Please let me know if this answers your question! &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Apr 2016 19:23:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alert-skipped-out-of-search-disk-space/m-p/279267#M12555</guid>
      <dc:creator>muebel</dc:creator>
      <dc:date>2016-04-08T19:23:11Z</dc:date>
    </item>
    <item>
      <title>Re: Alert skipped - out of search disk space</title>
      <link>https://community.splunk.com/t5/Alerting/Alert-skipped-out-of-search-disk-space/m-p/279268#M12556</link>
      <description>&lt;P&gt;What query could I use to ascertain how close a user is to the srchDiskQuota limit?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Apr 2016 15:30:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alert-skipped-out-of-search-disk-space/m-p/279268#M12556</guid>
      <dc:creator>adamblock2</dc:creator>
      <dc:date>2016-04-11T15:30:59Z</dc:date>
    </item>
  </channel>
</rss>

