We have set up a clustered Splunk enterprise environment and we have seen recently multiple scheduled searches getting skipped, ratio being observed varying from 80% to 99%.
Upon scrolling through the forum, we have observed that we can modify these values at limits.conf file.
My question is to confirm whether changing the concurrency value or search allocation quota for scheduled searches is advised as a best practice or would it be preparing some repercussions in the long run.
Also, what could be considered as a quick remedial action to mitigate this issue.
↧
