Reporting

Adding saved search using splunk CLI with enableSched does not work

hkaiser
Path Finder

Hello all,

I'm trying to define splunk saved-search using the splunk CLI.
In order to enable scheduling of a saved search, I identified the option "enableSched" in the savedsearch.conf. I would like to enable this option. However it looks like enableSched is not supported on the CLI.

However it looks like the parameter is not supported:

/opt/splunk/bin/splunk edit saved-search -name 'Test123' -enableSched '1'

An error occurred:

In handler 'savedsearch': Argument "enableSched" is not supported by this handler.

Is there another possiblity to enable scheduling of a report from the command line?

Also is there any possiblity to get a list of all possible parameters of splunk? Looks like /bin/splunk help does not provide much detail in this case and the splunk online documentation about the CLI does not provide such detail.

Thank you.

0 Karma
1 Solution

LukeMurphey
Champion

Instead of setting "enableSched", try "is_scheduled" instead. This should work:

/opt/splunk/bin/splunk edit saved-search -name 'Test123'  -is_scheduled '1'

I'm making a bug report to get them to make this more intuitive.

View solution in original post

LukeMurphey
Champion

Instead of setting "enableSched", try "is_scheduled" instead. This should work:

/opt/splunk/bin/splunk edit saved-search -name 'Test123'  -is_scheduled '1'

I'm making a bug report to get them to make this more intuitive.

arichman
Explorer

glad I found this!

0 Karma
Get Updates on the Splunk Community!

New Case Study Shows the Value of Partnering with Splunk Academic Alliance

The University of Nevada, Las Vegas (UNLV) is another premier research institution helping to shape the next ...

How to Monitor Google Kubernetes Engine (GKE)

We’ve looked at how to integrate Kubernetes environments with Splunk Observability Cloud, but what about ...

Index This | How can you make 45 using only 4?

October 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...