I am not able to see the schedule of the saved searches although they are cron scheduled . so when i am saving again the saved search the time can be seen but after some time it just does not show.
Hi @SN1
I have seen this before in a couple of scenarios, the first is when a search is created using the API or uploaded in a custom app but the search is invalid or has a macro which cannot be expanded, this causes the scheduler to not schedule the search but it does provide an error in the log. Do any of these search names appear in the _internal log with any errors?
How did you create the search? Was it done via manual changes to savedsearches.conf? API? UI? The other time I have seen this is when it was created via the API or manually in the conf:
Regarding enableSched, if you added the searches via the API then there can be some complications:
If you use the "/services/saved/search" endpoint then you need to use is_scheduled=1 instead of enableSched=1
If you use the "/servicesNS/<user>/<app>/configs/conf-savedsearches" then you need to use enableSched=1 but also I'm not 100% sure if changes will take effect without a reload/restart/search toggle when using this endpoint? Your mileage may vary.
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing
actually there is one thing that i forget to tell that i have made indexer standalone that these saved searches i have copied from search head
Does the user who created/modified the savedsearch have enough permissions?
Also whats the value of enableSched in savedsearches.conf. Make sure your search is having enableSched = 1 in savedsearches.conf.
#https://docs.splunk.com/Documentation/Splunk/9.4.2/Admin/Savedsearchesconf
Regards,
Prewin
Splunk Enthusiast | Always happy to help! If this answer helped you, please consider marking it as the solution or giving a Karma. Thanks!
it is made by me I have admin role, searches are not disabled and enableSched = 1.
When you edit the search in this state is it still initially enabled or disabled?
Did you check the config with btool?