https://community.splunk.com/t5/Reporting/Max-time-spent-in-per-result-alerts-issue/m-p/366626#M6324 <P>I'm running into an issue with a scheduled search not completing all of it's alert actions when it executes. The scheduled search has been set to run every minute and the warning will occur approximately every minute. We reduced the schedule to every 5 min and get the warning approximately every 5 minutes. This is the warning:</P> <P><CODE>04-27-2018 10:40:25.092 -0400 WARN SavedSplunker - Reached maximum amount of time allowed to spend in per-result alerts for savedsearch_id="nobody;app;search", sid="scheduler__user_Y3liZXJdrchyZWF0__RMD512364230b266f208_at_1524839700_11453_84568E04-6E8F-4D6B-7HF0C-1CD3DC88879B", max_alerts_time=300 (seconds), fired_alerts=172</CODE></P> <P>Regardless of the schedule the fired_alerts typically falls in the 150-190 range. In alert_actions.conf I did find the setting <CODE>maxtime = 5m</CODE> as a default. I changed that to <CODE>maxtime = 10m</CODE>. A btool shows that setting as applying but the warning still reflects a 300s time limit. Is there another setting to look at? I've dug through limits.conf, alert_actions.conf, and saved_searches.conf and didn't see anything but perhaps I missed something.</P> Tue, 29 Sep 2020 19:17:18 GMT mdsnmss 2020-09-29T19:17:18Z https://community.splunk.com/t5/Reporting/Max-time-spent-in-per-result-alerts-issue/m-p/366626#M6324 <P>I'm running into an issue with a scheduled search not completing all of it's alert actions when it executes. The scheduled search has been set to run every minute and the warning will occur approximately every minute. We reduced the schedule to every 5 min and get the warning approximately every 5 minutes. This is the warning:</P> <P><CODE>04-27-2018 10:40:25.092 -0400 WARN SavedSplunker - Reached maximum amount of time allowed to spend in per-result alerts for savedsearch_id="nobody;app;search", sid="scheduler__user_Y3liZXJdrchyZWF0__RMD512364230b266f208_at_1524839700_11453_84568E04-6E8F-4D6B-7HF0C-1CD3DC88879B", max_alerts_time=300 (seconds), fired_alerts=172</CODE></P> <P>Regardless of the schedule the fired_alerts typically falls in the 150-190 range. In alert_actions.conf I did find the setting <CODE>maxtime = 5m</CODE> as a default. I changed that to <CODE>maxtime = 10m</CODE>. A btool shows that setting as applying but the warning still reflects a 300s time limit. Is there another setting to look at? I've dug through limits.conf, alert_actions.conf, and saved_searches.conf and didn't see anything but perhaps I missed something.</P> Tue, 29 Sep 2020 19:17:18 GMT https://community.splunk.com/t5/Reporting/Max-time-spent-in-per-result-alerts-issue/m-p/366626#M6324 mdsnmss 2020-09-29T19:17:18Z https://community.splunk.com/t5/Reporting/Max-time-spent-in-per-result-alerts-issue/m-p/366627#M6325 <P>This allowed us to removed some caps in the limits.conf:</P> <PRE><CODE>[scheduler] action_execution_threads = 10 actions_queue_size = 10000 max_per_result_alerts =10000 max_per_result_alerts_time = 600 </CODE></PRE> Fri, 27 Apr 2018 15:59:17 GMT https://community.splunk.com/t5/Reporting/Max-time-spent-in-per-result-alerts-issue/m-p/366627#M6325 mdsnmss 2018-04-27T15:59:17Z