Getting Data In

Custom search command Values for these required options are missing: ...

Unige2021
Loves-to-Learn

I need to pass to my python custom search command two values: and y.

I found some examples where it's shown this:

 

 

x = Option(require=True, validate=validators.Fieldname())
y = Option(require=True, validate=validators.Fieldname())

 

 

 

Now I simply run my script by simply entering my_script x=50, y=25

Unfortunately I get this errors:

Illegal value: x=50
Illegal value: y=25
Values for these required options are missing: x, y

 

I cannot find neither the problem nor anyone who is facing this problem.

The code I copied from is an example taken from this url: Create a custom Splunk search commands with Python3 | HoldMyBeer (holdmybeersecurity.com)

 

Thank you in advance! 

Labels (1)
Tags (1)
0 Karma

s2_splunk
Splunk Employee
Splunk Employee

I am not an expert on this, but it seems like the way you have it implemented, the code will check if the values for x and y are field names, when you likely want to validate that they are integers.

Can you try changing to this and see if that helps:

x = Option(require=True, validate=validators.Integer())
y = Option(require=True, validate=validators.Integer())

If it does, specifying my_script x="abc" y="def" should throw an error.

As you currently have it, validation would support my_script x=some_event_field  y=some_other_event_field

At least that's my understanding on how it works. You can find a list of all implemented validators here. 

0 Karma
Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Reprocessing XML into Fixed-Length Events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

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