Hi All, Currently we could see few skipped schedule searches in our environment. From the deployment instance we have ran this query to get the list of skipped searches.
Query details:
dmc_set_index_internal sourcetype=scheduler (status="skipped")
Event details:
08-24-2017 03:12:12.981 -0400 INFO SavedSplunker - savedsearch_id="nobody;DA-deployment_monitor;_ACCELERATE_D4D707D0-38F3-4F47-A1AA-9DD305E110D0_DA-deployment_monitor_nobody_1a56f43bf8d5bf20_ACCELERATE_", search_type="report_acceleration", user="nobody", app="DA-deployment_monitor", savedsearch_name="_ACCELERATE_D4D707D0-38F3-4F47-A1AA-9DD305E110D0_DA-deployment_monitor_nobody_1a56f43bf8d5bf20_ACCELERATE_", priority=default, status=skipped, reason="The maximum number of concurrent auto-summarization searches on this instance has been reached", concurrency_category="summarization_scheduled", concurrency_context="instance-wide", concurrency_limit=2, scheduled_time=1503558600, window_time=0
APP Name : DA-deployment_monitor
hostname: test01
Event details:
08-24-2017 03:00:13.752 -0400 INFO SavedSplunker - savedsearch_id="splunk;sos;_ACCELERATE_D4D707D0-38F3-4F47-A1AA-9DD305E110D0_sos_splunk_9fd0bac7cd608f2c_ACCELERATE_", search_type="report_acceleration", user="splunk", app="sos", savedsearch_name="_ACCELERATE_D4D707D0-38F3-4F47-A1AA-9DD305E110D0_sos_splunk_9fd0bac7cd608f2c_ACCELERATE_",: priority=default, status=skipped, reason="The maximum number of concurrent historical scheduled searches on this instance has been reached", ", concurrency_context="instance-wide", concurrency_limit=4, scheduled_time=1503558000, window_time=0
App name: sos
hostname:test01
Event details:
08-24-2017 03:23:02.291 -0400 INFO SavedSplunker - savedsearch_id="nobody;search;_ACCELERATE_D4D707D0-38F3-4F47-A1AA-9DD305E110D0_search_nobody_365ca83246f2cca8_ACCELERATE_", search_type="report_acceleration", user="nobody", app="search", savedsearch_name="_ACCELERATE_D4D707D0-38F3-4F47-A1AA-9DD305E110D0_search_nobody_365ca83246f2cca8_ACCELERATE_", priority=default, status=skipped, reason="The maximum number of concurrent auto-summarization searches on this instance has been reached", concurrency_category="summarization_scheduled", concurrency_context="instance-wide", concurrency_limit=2, scheduled_time=1503559380, window_time=0
App name: search
hostname:test01
All these events are generated from the Deployment instance "test01"
Question :
1) Unable to find out the exact saved search name "ACCELERATE_D4D707D0-38F3-4F47-A1AA-9DD305E110D0_DA-deployment_monitor_nobody_1a56f43bf8d5bf20_ACCELERATE" from the events , so how to find that out inside the app directory
/opt/splunk/etc/apps/DA-deployment_monitor/default/savedsearches/ -- I could see many queries saved as scheduled searches, but could not find the exact name mentioned as mentioned in the above events.
2) How to fix this issue, I could see these reasons from events
a) "The maximum number of concurrent auto-summarization searches on this instance has been reached"
b) concurrency_category="historical_scheduled
c) concurrency_category="summarization_scheduled"
d) concurrency_limit=2
e) scheduled_time=1503558600
f) window_time=0
g) concurrency_context="instance-wide"
Kindly guide me how to fix this issue.
thanks in advance.
... View more